Date: Thu, 24 Mar 2016 15:36:16 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: toolchain@FreeBSD.org Subject: CXXSTD=c++11 Message-ID: <56F46BE0.7080909@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --KsREgjOKCCaI05R0f0JlkgGU8Blf7huG4 Content-Type: multipart/mixed; boundary="c7d4setxfNWE5Epfwa5U3dw27U6d1AlLL" From: Bryan Drewery <bdrewery@FreeBSD.org> To: toolchain@FreeBSD.org Message-ID: <56F46BE0.7080909@FreeBSD.org> Subject: CXXSTD=c++11 --c7d4setxfNWE5Epfwa5U3dw27U6d1AlLL Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Is there any problem with forcing -std=3Dc++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++. It seems to be the problem at https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-October/001757= =2Ehtml which I've fixed in an upcoming commit to properly pass -std=3Dc++11 to the lib32 build in CXXFLAGS. --=20 Regards, Bryan Drewery --c7d4setxfNWE5Epfwa5U3dw27U6d1AlLL-- --KsREgjOKCCaI05R0f0JlkgGU8Blf7huG4 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 iQEcBAEBAgAGBQJW9GvkAAoJEDXXcbtuRpfPq94H/0R/F6FMHhsqa4YcAdboKCEm j/u3IoyBmp5/PN6BAEKm8e8ebZ09HSTQzhw/Jx4VKl+bVdphMyfKdwF236KfM+UR 1es5bZQYI/Tx5pXBPdVCbFx5X3v6qRmSwFBWxmkHTnHW+MMFhLi2GBvP+e+lrFab 4Iy55bWVV+MStEmY7ClyRCKkQdv0474slsfo6HlR0Ig+bzwt4fQTjFHOYWFs7D67 vNVFpM3biystxqIl7DrImd2u0VrZVJrMM6krT0qs+BMX4uzIZQJlyqQuOUWyShAN Ltj8hdUSH2XpZKA+sdgk8R0ucrO1tpjYYjVOYqrE+V+bbTJSy2q0QCmn+yoZHyQ= =L4WD -----END PGP SIGNATURE----- --KsREgjOKCCaI05R0f0JlkgGU8Blf7huG4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56F46BE0.7080909>