[MacPorts] #45307: clang-3.4 not picking up C++11 headers on 10.6.8
MacPorts
noreply at macports.org
Fri Oct 10 06:51:49 PDT 2014
#45307: clang-3.4 not picking up C++11 headers on 10.6.8
--------------------------+--------------------------------
Reporter: rjvbertin@… | Owner: macports-tickets@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: duplicate | Keywords:
Port: clang-3.4 |
--------------------------+--------------------------------
Comment (by jeremyhu@…):
Replying to [comment:9 rjvbertin@…]:
> Replying to [comment:8 jeremyhu@…]:
>
> > > Will installing port:libcxx and port:libcxxabi (mostly containing
libraries) address the issue of clang-3.4 not finding the correct
headerfiles?
> > Yes, assuming you use -stdlib=libc++ as well
>
> Can one have port:libcxx and port:libcxxabi installed and activated
without interference with existing binaries or builds as long as one does
NOT use -stdlib=libc++, on 10.6?
Of course. If you don't use -stdlib=libc++, clang will use libstdc++ on
Snow Leopard.
> > The clang compilers will only use the C++ runtimes in /usr/lib. There
is no intention of supporting other C++ runtimes
>
> It seems it shouldn't be that hard to create a backwards compatible
updated libstdc++ that can replace the one in /usr/lib, but priorities are
priorities ...
It actually is not only difficult but license-restrictive.
> >we have a way for users on SnowLeopard through Mountain Lion to also
use libc++.
>
> One that requires rebuilding all binaries that contain compiled C++
code, right?
Yes.
> Maybe that could be an automatic process comparable to +universal ...
but backed up by the build bots? Still a huge pile of work, esp. with
clang-mp-3.4 being as slow as it is ...
That was discussed a few months ago.
--
Ticket URL: <https://trac.macports.org/ticket/45307#comment:10>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list