Date: Thu, 24 Mar 2016 23:44:02 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: toolchain@FreeBSD.org Subject: Re: CXXSTD=c++11 Message-ID: <43ABA5F3-60E0-4A29-9698-B345A3DA0A8B@FreeBSD.org> In-Reply-To: <56F46BE0.7080909@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 24 Mar 2016, at 23:36, Bryan Drewery <bdrewery@FreeBSD.org> wrote: > > Is there any problem with forcing -std=c++11 for all CXX/LIB_CXX builds > now? We do this when using an external GCC since it doesn't default to > the c++11 standard quite yet. As far as I understand, we require c++11 > to build clang/libc++. Yes, but it already passes -std=c++11 in the correct places, as far as I know. E.g. during the clang and libc++ builds. > It seems to be the problem at > https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-October/001757.html > which I've fixed in an upcoming commit to properly pass -std=c++11 to > the lib32 build in CXXFLAGS. Hm, is this occuring during the build of libcxxrt, or of libc++? If it is the former, then it seems that the system headers don't properly declare _Static_assert() in that case. I have no clue as to why, though maybe it's picking something up from gcc's famously "fixed" standard headers? -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.29 iEYEARECAAYFAlb0bbgACgkQsF6jCi4glqPmmgCfa1W4Uouk2F0pWc9e2cIybOPX seQAn1yoe0dAR1YhQamNkMiwcpKoKYnb =N+KF -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43ABA5F3-60E0-4A29-9698-B345A3DA0A8B>