[MacPorts] #35757: clang in MacPorts has problems with "libc++"

MacPorts noreply at macports.org
Mon Aug 20 10:36:28 PDT 2012


#35757: clang in MacPorts has problems with "libc++"
-------------------------------------+--------------------------------------
 Reporter:  michael.lehn@…           |       Owner:  macports-tickets@…                   
     Type:  defect                   |      Status:  new                                  
 Priority:  High                     |   Milestone:                                       
Component:  ports                    |     Version:  2.1.2                                
 Keywords:                           |        Port:                                       
-------------------------------------+--------------------------------------
 clang++ compilers (any version) installed with MacPorts have problems when
 C++11 are being used.  That's because the C++11 can not  be found.

 I attached a simple C++ source file with 3 lines of code.  It can not be
 compiled with an MacPort installation of any clang compiler.  Try

 clang++ main.cc
  #fails because one header is c++11 specific

 clang++ -std=c++11 main.cc
  #fails because <type_traits> can not be found

 clang++ -std=c++11 -stdlib=libc++ main.cc
  #fails because <complex> can not be found

 Please understand, a clang++ installation that can not be used with C++11
 is pretty useless.

 The problem was discussed on the clang developer mailing list:
 http://lists.cs.uiuc.edu/pipermail/cfe-dev/2012-August/023867.html

 Douglas Gregor <dgregor at apple.com> says: "MacPorts needs to start
 installing libc++ headers relative to the clang binaries it installs; they
 can look at where those headers land in an Xcode-installed Clang."

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


More information about the macports-tickets mailing list