[MacPorts] #35770: gcc ports should not include a C++ runtime

MacPorts noreply at macports.org
Tue Sep 11 15:56:07 PDT 2012


#35770: gcc ports should not include a C++ runtime
--------------------------------------------------+------------------------
  Reporter:  jeremyhu@…                           |      Owner:  jeremyhu@…
      Type:  defect                               |     Status:  closed
  Priority:  Normal                               |  Milestone:
 Component:  ports                                |    Version:  2.1.2
Resolution:  fixed                                |   Keywords:  libstdc++
      Port:  gcc43 gcc44 gcc45 gcc46 gcc47 gcc48  |
--------------------------------------------------+------------------------

Comment (by jeremyhu@…):

 Replying to [comment:26 jonesc@…]:
 > I totally disagree things are better now., the previous situation seemed
 much better to me. At least we could actually compile using the gcc
 compilers... Maybe there was some theoretical instability mixing libstdc++
 versions, but I never had any.

 Comment 2 above shows that it's not a theoretical instability.

 > Things changes have caused various ports to stop working. For instance
 all the gcc variants the root port provide. root provides a interactive
 C++ environment so the user really may have a reason for wanting a
 particular gcc version. Not to mention fortran support.
 >
 > Please considering reverting this, until you have the better solution
 ready.

 I will try adding a libstdc++ port based on libc++sup as an interim
 solution, but in order to really fix this, someone will need to port it to
 libc++abi to be compatible with the host runtime.

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


More information about the macports-tickets mailing list