[MacPorts] #34288: clang ports use the old/dated libstdc++ from the host (gcc-4.2 based)

[MacPorts]

#34288: clang ports use the old/dated libstdc++ from the host (gcc-4.2 based)
-----------------------------------------------------------------------+----
  Reporter:  christophe.prudhomme@…                                    |       Owner:  jeremyhu@…           
      Type:  defect                                                    |      Status:  closed               
  Priority:  Normal                                                    |   Milestone:                       
 Component:  ports                                                     |     Version:  2.0.4                
Resolution:  worksforme                                                |    Keywords:                       
      Port:  clang-2.9 clang-3.0 clang-3.1 clang-3.2 libstdc++ libc++  |  
-----------------------------------------------------------------------+----

Comment(by jeremyhu@…):

 Right, I need to talk to some people who know more about the low level
 runtimes to figure out what the right course of action is.  I know for
 certain that it's not possible to have more than one ObjC runtime in a
 single process, but I don't know how the C++ runtimes can or can't co-
 exist.  Most of C++ is implemented in the headers themselves as templates,
 and I am worried that passing objects between the g++ 4.7's libstdc++
 runtime and clang++'s libc++ runtime might be problematic.

 The correct solution may end up being the removal of the libstdc++
 runtimes from the gcc ports.  In fact, even if we do provide a C++ runtime
 in MacPorts, I'd prefer to have that as a separate port rather than
 separately from each compiler.

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