Date: Tue, 18 Sep 2012 09:31:57 +0100 From: David Chisnall <theraven@FreeBSD.org> To: Brooks Davis <brooks@FreeBSD.org> Cc: toolchain@FreeBSD.org Subject: Re: enabling libc++ by default when building with clang Message-ID: <1B405D52-65B8-44A2-B350-0973A8B254CB@FreeBSD.org> In-Reply-To: <20120917191028.GA42648@lor.one-eyed-alien.net> References: <20120917191028.GA42648@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 Sep 2012, at 20:10, Brooks Davis wrote:
> One key question is, when do we want to throw this switch? Do we do =
it
> now so people using clang start using it sooner or do we wait until
> we've switched the default compiler and things have settled a bit?
As dim says, enabling it does not mean requiring things to use it. I =
would like to flip this switch as soon as possible so that it's easy for =
ports people maintaining C++ ports to see if their stuff breaks with =
-stdlib=3Dlibc++. A few have already tested this, but I'd like to see =
much wider testing. =20
The more important switches to worry about are:
- Changing the default for -stdlib=3D to libc++ (it's currently =
libstdc++. I think I'll probably make it libc++ when std=3D{c,gnu}++11 =
soon)
- Removing libstdc++ from base and putting it in the compat9 port.
These have the potential to impact users significantly. Simply having =
libc++.{so,a} on their system does not unless they explicitly choose to =
test it.
David=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1B405D52-65B8-44A2-B350-0973A8B254CB>