| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 20/12/13 06:56 AM, Sven Eden wrote: |
| 5 |
> |
| 6 |
> So basically C++11 <-> C++03 is no problem at all (unless you |
| 7 |
> *export* certain symbols [2]), but combining C++11 from different |
| 8 |
> gcc versions is nowhere guaranteed to work. |
| 9 |
> |
| 10 |
> Cheers |
| 11 |
> |
| 12 |
> Sven |
| 13 |
> |
| 14 |
> |
| 15 |
> [1] : https://lwn.net/Articles/552831/ [2] : |
| 16 |
> http://gcc.gnu.org/wiki/Cxx11AbiCompatibility |
| 17 |
> |
| 18 |
|
| 19 |
|
| 20 |
Aha... so what we should probably be doing then is filtering out |
| 21 |
- --std=c++11 until gcc-4.9 or whatever version is released, that will |
| 22 |
standardize things, so that we don't end up with systems that have a |
| 23 |
mix-and-match. |
| 24 |
|
| 25 |
And probably alert users using earlier versions of gcc that if they |
| 26 |
enable --std=c++11, they should expect to 'emerge -e @world' on any |
| 27 |
compiler switch. |
| 28 |
|
| 29 |
|
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 32 |
|
| 33 |
iF4EAREIAAYFAlK0XdEACgkQ2ugaI38ACPB2WgEAtnLeonyTFCF5cMEIi0kSIHZ/ |
| 34 |
RZcgjzRbojT3YejvMmkA/2v/qC7Cy58QAgz7oEC5z+KvPUVBJ79Ana0+rrPoq9TM |
| 35 |
=pn2S |
| 36 |
-----END PGP SIGNATURE----- |
Archives