[MacPorts] #36204: gcc47 empty string issue

MacPorts noreply at macports.org
Wed Sep 19 05:17:21 PDT 2012


#36204: gcc47 empty string issue
--------------------------+--------------------------------
  Reporter:  rob.patro@…  |      Owner:  macports-tickets@…
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.1.2
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------------------

Comment (by ecronin@…):

 Around comment 17 in that ticket is when jeremy switched all the gcc ports
 to use the system stdlib and things completely broke for the gccs.  He
 then created ports for libstdcxx and libstdcxx-devel which is the gcc
 stdlib as a stop-gap fix and made all the gcc ports depend on a single gcc
 stdlib so that at least things compiled with gcc4x and gcc4y can be linked
 together safely.  All the macports clangs and llvms now use the system
 stdlib so they can be linked together with things compiled with the system
 toolchain.  The two different families can't easily/safely be mixed
 though.

 The "Furthermore... " part of comment 23 and comment 25 is what would need
 to be done to get the gcc ports to safely link with libraries built using
 the system stdlib, but it hasn't been done and someone other than jeremy
 would have to undertake it it sounds like.

-- 
Ticket URL: <https://trac.macports.org/ticket/36204#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list