[MacPorts] #34288: clang ports use the old/dated libstdc++ from the host (gcc-4.2 based)
MacPorts
noreply at macports.org
Mon Sep 10 05:41:29 PDT 2012
#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: fixed | Keywords:
Port: clang-2.9 clang-3.0 clang-3.1 clang-3.2 libstdc++ libc++ |
-----------------------------------------------------------------------+----
Comment(by stephen@…):
Can some please explain what the new changes are? I see that installing
clang >= 3.0 now also installs headers from libc++ in
/opt/local/libexec/llvm-3.1/lib/c++/v1 and that's where mp-clang will be
looking for standard library headers. But as far as I can tell, it doesn't
have a matching libc++.dylib and still links against the system one in
/usr/lib.
Is this intended and safe? The 2 sets of v1 headers are not the same. Can
the difference cause any runtime issue?
Also I am trying this in OS X 10.7 which is shipped with libc++. What
happens in 10.6? Does MacPorts installs a copy of libc++ (and the ABI lib)
with clang?
Thanks.
--
Ticket URL: <https://trac.macports.org/ticket/34288#comment:25>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list