> On Mar 24, 2016, at 4:42 PM, Bryan Drewery <[email protected]> wrote: > > On 3/24/2016 3:39 PM, Warner Losh wrote: >> >>> On Mar 24, 2016, at 4:36 PM, Bryan Drewery <[email protected]> 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. >> > > *sigh*
It wouldn’t take too much to unbreak the build for those platforms, though. And there’s been talk of kicking out gcc entirely for 11, which would force these ports to external toolchain builds, which wouldn’t be broken. So with the deadline 1 month away, what’s being done to de-orbit gcc, if anything? Warner
signature.asc
Description: Message signed with OpenPGP using GPGMail
