Date: Thu, 24 Mar 2016 16:39:58 -0600 From: Warner Losh <imp@bsdimp.com> To: Bryan Drewery <bdrewery@freebsd.org> Cc: toolchain@FreeBSD.org Subject: Re: CXXSTD=c++11 Message-ID: <635A0A5E-63F2-4D42-B6D5-0E841AA713FE@bsdimp.com> In-Reply-To: <56F46BE0.7080909@FreeBSD.org> References: <56F46BE0.7080909@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] > On Mar 24, 2016, at 4:36 PM, 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++. > > 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. Wouldn’t that break the spark and mips builds if we did it always? They are the last stragglers to not have a working, fully vetted clang in the tree. Warner [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJW9Gy/AAoJEGwc0Sh9sBEAp34P/jpr4q00AMoUcWVYy+B2FMPz EuGAt+eiJjUgNXz2AczEgqCQjN0BXmsWySNyxl6uqmP1jwIJhluUdp8qckgzSlix dh3do1hiRCDAePbhYGfXJcw9dqKWHAXyortYVt2MZEr0UzmY5Scoye9tALJLthat QuyaRgO9za9/R6zsArmxr2nHp/KxTMn5lCoxT/D/fE7JWwpDqFb/siMZk8/xc/4Z yHhYeEhkiWBBAV4/J4eufF9y6L9wxfa4lZUmtkS3cF5fwh2tKFgMkDyrCOft26uC pYTmdd+ybSkS+Vfvfk6tD7csQgo3W8kLwdsVIbpELL2NnDS7Utj+MckZrMWF8dbG oNSkPsOSigNsCLxxJUtEqtnmcoap5JDErA6ukrQBgsxVqUVfC7Da1JzpFhiWs3/p 5XOOksowtvkHCw7xKNBjyaIBcw4cBX2XguU8VvgmEDj8UQPLaWpavp+f7XA2ep0i XI9xBwY5+hSnvEF7euhb7YmkiDPAEahpUejXulaByUVZIeX9T4nynFsnJsZaDvBU /FTJbR9W1qEuf5EOTfmtmaBN13Yr67n0opsAxE7sJJm8hHHQSVlS7dlWRH2J9w4R BV87hsdVJBlkphOIXHAluw+RmbdkEP7GbmEGrRirgXswkI07ZLFetgAhTQ8ZfZV+ 4N2cZzT/JQ3huxSCxlz0 =uQ/1 -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?635A0A5E-63F2-4D42-B6D5-0E841AA713FE>