Date: Thu, 24 Mar 2016 16:44:56 -0600 From: Warner Losh <imp@bsdimp.com> To: Bryan Drewery <bdrewery@freebsd.org> Cc: toolchain@FreeBSD.org Subject: Re: CXXSTD=c++11 Message-ID: <64C513BC-2F49-42B0-A818-7A57421C7553@bsdimp.com> In-Reply-To: <56F46D63.10303@FreeBSD.org> References: <56F46BE0.7080909@FreeBSD.org> <635A0A5E-63F2-4D42-B6D5-0E841AA713FE@bsdimp.com> <56F46D63.10303@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_F1B2E9BB-17A6-4AE8-BB44-AA920F0E7383 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Mar 24, 2016, at 4:42 PM, Bryan Drewery <bdrewery@freebsd.org> = wrote: >=20 > On 3/24/2016 3:39 PM, Warner Losh wrote: >>=20 >>> On Mar 24, 2016, at 4:36 PM, Bryan Drewery <bdrewery@freebsd.org> = wrote: >>>=20 >>> 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++. >>>=20 >>> 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=3Dc++11 = to >>> the lib32 build in CXXFLAGS. >>=20 >> Wouldn=E2=80=99t 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. >>=20 >=20 > *sigh* It wouldn=E2=80=99t take too much to unbreak the build for those = platforms, though. And there=E2=80=99s been talk of kicking out gcc entirely for 11, which = would force these ports to external toolchain builds, which wouldn=E2=80=99t be broken. So with the deadline 1 month away, what=E2=80=99s being done to de-orbit = gcc, if anything? Warner --Apple-Mail=_F1B2E9BB-17A6-4AE8-BB44-AA920F0E7383 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJW9G3oAAoJEGwc0Sh9sBEA3vwP/AlXIHAqmz+8/DTwCxPCALcZ shP5oQ2EFtY5Nz4dkSuexGL4M725GA7DxmVsEz4vKIKxmDj84Q8mUQp3hTnxUjwn ENVXLpSstOBbmMnXIZiOYJuGY2BNnDL6I6p8bkqJqC8z8/QJA95SApxpXh+R37su eGpWhjr9Vae9kKO9KLSQ0HXy3WrvRmppONsKbb786DKZRs/H8fAsRfOjl8KR0yeD DHEgibPx57xEFHFRsS6zZcdv8Gc/Ba9TDDAETqlztKgayyC4sfR+Lw74BXm1U9OH bmfplGTf1K0HH0Ajucy5x8Ra4gwowLccS4peW9SIXX6QLk+9IuXGXontvsnftAqs cEMDuBN7ErVJtjXLzWdHVYycBpIvmDzWEp4UGOXmlb0bRH88cm6wSoyCGKKfjGjo vdvuuaveOts/rgWqx2TyFr7IOegavQb38wIzENcTQLq2YRlPxx+563tDHMrn3Etu DY7IKBMh+ygEw+IJO7kv1bmi4JOqHMXp83WzfJ/z+DqBQTfHdaY4JIbPAmm394/K SVT60OqQbBbkMn3x9JCtNgo2JD6zfKa5bPEpbcjWCaKh4bt9D7RHC7xhCLSdUPpw LGG4/o4vbiB+NB9kYrpy3iv4g47I2QMNaxUwG5ubQzZ3ix7aEubriQS8UwrgeJmF RdfQFKyQ+DXUTDw76TrR =CvDy -----END PGP SIGNATURE----- --Apple-Mail=_F1B2E9BB-17A6-4AE8-BB44-AA920F0E7383--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?64C513BC-2F49-42B0-A818-7A57421C7553>