-stdlib=libc++ fails for some ports

[Dimitry Andric]

On 2012-11-29 10:59, Volodymyr Kostyrko wrote:
> When compiling databases/db5 with CFLAGS+= -stdlib=libc++ I got this:
>
> libtool: compile:  c++ -c -I. -I./../src -D_THREAD_SAFE -O2 -pipe
> -march=native -fno-strict-aliasing -stdlib=libc++ ../lang/cxx/cxx_db.cpp
>    -fPIC -DPIC -o .libs/cxx_db.o
> In file included from ../lang/cxx/cxx_channel.cpp:13:
> In file included from ./db_cxx.h:55:
> In file included from /usr/include/c++/v1/iostream:38:
> In file included from /usr/include/c++/v1/ios:216:
> In file included from /usr/include/c++/v1/__locale:15:
> In file included from /usr/include/c++/v1/string:434:
> In file included from /usr/include/c++/v1/algorithm:590:
> In file included from /usr/include/c++/v1/initializer_list:47:
> /usr/include/c++/v1/cstddef:64:61: error: expected class member or base
> class name
>       _LIBCPP_ALWAYS_INLINE _LIBCPP_CONSTEXPR nullptr_t() : _(0) {}
>                                                               ^
> ./db_int.h:445:16: note: expanded from macro '_'
> #define _(msg)  msg     /* Replace with localization function. */
>                   ^
>
> The problem is actually on libc++ side and has been fixed upstream:
>
> http://llvm.org/viewvc/llvm-project?view=rev&revision=167038

Yes, David imported a new libc++ snapshot, including this fix, into head
in r242945.  He did not set an MFC period at the time, so I am not sure
what his plans are. :-)