| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 19/12/13 04:07 AM, Michał Górny wrote: |
| 5 |
> Dnia 2013-12-19, o godz. 09:58:25 Sven Eden <sven.eden@×××.de> |
| 6 |
> napisał(a): |
| 7 |
> |
| 8 |
>> So I'd go the reverse way. Make CXXFLAGS="-std=c++11" the |
| 9 |
>> default, and only override this for packages that do fishy stuff |
| 10 |
>> and break with it. |
| 11 |
> |
| 12 |
> How can we do that? I think the only possibility is to patch gcc |
| 13 |
> and change the default... |
| 14 |
> |
| 15 |
|
| 16 |
A change in profiles? 14.0/* adds that to the default CXXFLAGS in |
| 17 |
base, new stage3's etc are all rolled with this. We recommend |
| 18 |
migration to 14.0 profile and have a check somewhere about |
| 19 |
"-std=c++11" missing from CXXFLAGS in case it's overridden in |
| 20 |
make.conf, so users put it in place? |
| 21 |
|
| 22 |
Now just a quick question about this; is an emerge -e @world going to |
| 23 |
be necessary to make end-user systems work after such a change? it's |
| 24 |
sounding like it would be .... |
| 25 |
|
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 34 |
|
| 35 |
iF4EAREIAAYFAlKzCf0ACgkQ2ugaI38ACPBBoAD/Y/e01CuaFf/40HfZMvGoknZg |
| 36 |
oK9k5kX5HPCB30xNTYUA/jzg6mfTL1h6RYSgitKUQ8un3ewJTV9Nybmgr3nuvxr2 |
| 37 |
=SBQP |
| 38 |
-----END PGP SIGNATURE----- |
Archives