Date: Thu, 24 Mar 2016 15:45:47 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Dimitry Andric <dim@FreeBSD.org> Cc: toolchain@FreeBSD.org Subject: Re: CXXSTD=c++11 Message-ID: <56F46E1B.4010605@FreeBSD.org> In-Reply-To: <43ABA5F3-60E0-4A29-9698-B345A3DA0A8B@FreeBSD.org> References: <56F46BE0.7080909@FreeBSD.org> <43ABA5F3-60E0-4A29-9698-B345A3DA0A8B@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --taLDJrjlHjQfNGrTl5cmVa4te6OCEupEW Content-Type: multipart/mixed; boundary="E4jjuhsCCXh86fHJrS7ccsGdC98oUk034" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Dimitry Andric <dim@FreeBSD.org> Cc: toolchain@FreeBSD.org Message-ID: <56F46E1B.4010605@FreeBSD.org> Subject: Re: CXXSTD=c++11 References: <56F46BE0.7080909@FreeBSD.org> <43ABA5F3-60E0-4A29-9698-B345A3DA0A8B@FreeBSD.org> In-Reply-To: <43ABA5F3-60E0-4A29-9698-B345A3DA0A8B@FreeBSD.org> --E4jjuhsCCXh86fHJrS7ccsGdC98oUk034 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 3/24/2016 3:44 PM, Dimitry Andric wrote: > On 24 Mar 2016, at 23:36, Bryan Drewery <bdrewery@FreeBSD.org> wrote: >> >> Is there any problem with forcing -std=3Dc++11 for all CXX/LIB_CXX bui= lds >> now? We do this when using an external GCC since it doesn't default t= o >> the c++11 standard quite yet. As far as I understand, we require c++1= 1 >> to build clang/libc++. >=20 > Yes, but it already passes -std=3Dc++11 in the correct places, as far a= s I > know. E.g. during the clang and libc++ builds. >=20 >=20 >> It seems to be the problem at >> https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-October/001= 757.html >> which I've fixed in an upcoming commit to properly pass -std=3Dc++11 t= o >> the lib32 build in CXXFLAGS. >=20 > 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, thoug= h > maybe it's picking something up from gcc's famously "fixed" standard > headers? >=20 libcxxrt. My fix also includes passing the proper -isystem =3D/usr/include/c++/v1 p= ath. I'll try without the -std change. --=20 Regards, Bryan Drewery --E4jjuhsCCXh86fHJrS7ccsGdC98oUk034-- --taLDJrjlHjQfNGrTl5cmVa4te6OCEupEW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJW9G4bAAoJEDXXcbtuRpfPADAH/1hARk/DofVo8nFz5WFh59JX /JBvuGlE99SaHqg6nF6X4k/lTIv8z4JkZ9t51RoAhc5iL8JCMG5W0YgOlKoDpPRS tefslGA7gbqtNbemzsp6cdXQLG6uTjOj0jeK6KEaR2glwKzYgC8p9m+P+MwY7FRf CAnu6K/d+plDu4Ek+MWQyZHSbujiZ5f2L8/gRZMz2+KEuK5bih7u+T7ut9AVO8EY bDuCRC0uVXv159nLPQWq0/mXOFBbo17VprjNvQqK/NwQKryRfrcGipy3mSDFbZbx 3TzQpRZLPPgrvPv9WHKB8sEZS91YL1HQGmiraV7E0+J3vdDLBiOLUdw3VaAnSRE= =HuRj -----END PGP SIGNATURE----- --taLDJrjlHjQfNGrTl5cmVa4te6OCEupEW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56F46E1B.4010605>