[MacPorts] #35757: clang-2.9, clang-3.0, clang-3.1, clang-3.2: problems with "libc++" (was: clang in MacPorts has problems with "libc++")

[MacPorts]

#35757: clang-2.9, clang-3.0, clang-3.1, clang-3.2: problems with "libc++"
-------------------------------------+--------------------------------------
 Reporter:  michael.lehn@…           |       Owner:  jeremyhu@…                                
     Type:  defect                   |      Status:  new                                       
 Priority:  Normal                   |   Milestone:                                            
Component:  ports                    |     Version:  2.1.2                                     
 Keywords:                           |        Port:  clang-2.9, clang-3.0, clang-3.1, clang-3.2
-------------------------------------+--------------------------------------
Changes (by ryandesign@…):

  * priority:  High => Normal
  * owner:  macports-tickets@… => jeremyhu@…
  * port:  => clang-2.9, clang-3.0, clang-3.1, clang-3.2


Old description:

> 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."

New description:

 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#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS