[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:  assigned                                                
 Priority:  Normal                                |   Milestone:                                                          
Component:  ports                                 |     Version:  2.0.4                                                   
 Keywords:                                        |        Port:  clang-2.9 clang-3.0 clang-3.1 clang-3.2 libstdc++ libc++
--------------------------------------------------+-------------------------

Comment(by jeremyhu@…):

 Actually, ... I dunno.

 I don't really like the idea of having multiple C++ runtimes in the same
 address space, so I'm not sure I want to go down this road.  I need to
 think about this some more.

 I think our choices should be:
   * provide a single runtime that all of our compilers use (as opposed to
 a different dylib for each compiler)
   * All of our compilers use the host's C++ runtime

 The second is consistent with the ObjC runtime, and it is what clang-X.X
 and apple-gcc42 do.

 Lion provides libc++, so clang-X.X use this newer runtime on Lion.

 I'm guessing that you are on SL because that would be consistent with the
 failure that you reported.  '#include <boost/signals2.hpp>' compiles fine
 for me on Lion.

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