On 10/20/14 15:49, Anthony G. Basile wrote:
On 10/20/14 14:35, Ian Stakenvicius wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 20/10/14 06:58 AM, Anthony G. Basile wrote:
On 10/20/14 04:23, Alexander Berntsen wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 20/10/14 08:36, Luca Barbato wrote:
Since gcc-4.7 there is a -std=c++11 option, do not use it since
it breaks the ABI, resulting in a non-functional system.
Since gcc-4.7 there is a -std=c++11 option, do not use it
{+yet+} since it breaks the ABI, resulting in a non-functional
system.
Yes. Eventually we'll have to clear the road for this. However,
I don't think we'll ever want to support a mixed abi system.
Can we, even? Would it be a mixed-abi system or a multi-abi system?
The correct thing for upstream to do is to bump the soname. But right
now, we have:
readelf -d /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libstdc++.so.6.0.17 |
grep SONAME
readelf -d /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libstdc++.so.6.0.18 |
grep SONAME
readelf -d /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.1/libstdc++.so.6.0.20
| grep SONAME
all yielding
0x000000000000000e (SONAME) Library soname: [libstdc++.so.6]
Oh wait sorry, that's a confusion with the gcc-4.7 vs 4.8 problem. As
far as the c++98 vs c++11, I'm not sure.
--
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197
