Date: Thu, 24 Mar 2016 15:42:43 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Warner Losh <imp@bsdimp.com> Cc: toolchain@FreeBSD.org Subject: Re: CXXSTD=c++11 Message-ID: <56F46D63.10303@FreeBSD.org> In-Reply-To: <635A0A5E-63F2-4D42-B6D5-0E841AA713FE@bsdimp.com> References: <56F46BE0.7080909@FreeBSD.org> <635A0A5E-63F2-4D42-B6D5-0E841AA713FE@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Pa1pf4vnm3SmMe4etxtdeNd4usDb5ELng Content-Type: multipart/mixed; boundary="S0OS0p32cIXBkfe8DaeTIpq6OeatIvvB3" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Warner Losh <imp@bsdimp.com> Cc: toolchain@FreeBSD.org Message-ID: <56F46D63.10303@FreeBSD.org> Subject: Re: CXXSTD=c++11 References: <56F46BE0.7080909@FreeBSD.org> <635A0A5E-63F2-4D42-B6D5-0E841AA713FE@bsdimp.com> In-Reply-To: <635A0A5E-63F2-4D42-B6D5-0E841AA713FE@bsdimp.com> --S0OS0p32cIXBkfe8DaeTIpq6OeatIvvB3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 3/24/2016 3:39 PM, Warner Losh wrote: >=20 >> On Mar 24, 2016, at 4:36 PM, Bryan Drewery <bdrewery@freebsd.org> wrot= e: >> >> 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++. >> >> 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 > Wouldn=E2=80=99t that break the spark and mips builds if we did it alwa= ys? They are the > last stragglers to not have a working, fully vetted clang in the tree. >=20 *sigh* --=20 Regards, Bryan Drewery --S0OS0p32cIXBkfe8DaeTIpq6OeatIvvB3-- --Pa1pf4vnm3SmMe4etxtdeNd4usDb5ELng 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 iQEcBAEBAgAGBQJW9G1jAAoJEDXXcbtuRpfPOvMH/RU+AdDNI3Kd5owsQTykvgiH d3UyU7oKTa30OM5R3b5rUjdkn9wiGCBGNqqVCwowl3OiKEsBULwk8b8cNqHA/0BL 2pTw35zjslrpEgtRCGB1fIIj0EvJM1JbZPSDQiieUNGvVXzZnp3mjASoxhZmqvvW FOU3Xi4Wq9i3vqk2s15gEqYJ6AGBG3FgQFLbKv4EpyXidNi1oWGMRwIp4LGIK+v1 oz0u7AzKvcgY6ZKN3ShIxx1Ls6Oy0sL7nw9axvLqYzRNZrej3JGN0xFJ5NNAEVhU 2ifId8hXNPkGyTlZJHJR5JTgYj17+6InWO+qipAYLyXKZLIXWQ8yU+CYTeppBbE= =J7Jb -----END PGP SIGNATURE----- --Pa1pf4vnm3SmMe4etxtdeNd4usDb5ELng--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56F46D63.10303>