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

[MacPorts]

#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:24 help@…]:
 > libstdc++ port isn't what I have in mind. I wanted a way for gcc46 to
 use system libstdc++. I tried just now to replace
 /opt/local/include/gcc46/c++/ content with /usr/include/c++/4.2.1/, but
 gcc failed to understand them correctly and exited with some error about
 _is_pod in cpp_type_traits.h. So incompatibility is both ways :( Unless
 you have something more up your sleeve

 What I have "up my sleeves" is libstdc++ STL on top of libc++abi.  That
 has been done by Apple for gcc-4.2's libstdc++ as shipped in Lion and
 Mountain Lion.  If you want newer libstdc++, you will need to merge those
 changes into newer gcc and create a new port for them.  As I mentioned,
 the license of newer gcc prevents me from doing this work, but hopefully
 someone able to work on GPL3 will be willing to touch it.

 > , it basicly means that these gcc ports currently do not work reliably
 and therefore more or less useless.

 So... basically things are still broken, but they're now broken
 differently (and perhaps more obviously).  I prefer obvious breakage over
 invisible breakage, so I'll take this as progress.

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