Mentioned GCC warning informs about situations where library may be
theoretically successfully linked with another one built with
incompatible ABI. For more info on this topic, see
https://developers.redhat.com/blog/2015/02/05/gcc5-and-the-c11-abi/)
https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html
Unfortunately, the only way to make this warning disappear is explicitly
put explicit abi_tag attribute to every single affected symbol, which
seems excessive and does not help readibility.
Notably, our internet research seem to suggest that this issue (linking
code built with old and new ABI) is almost never occuring in practice,
as all packages for given OS are by convention built with the same
version.
Judging from the relative lack of related problems, tutorials or general
discussion about this topic, -Wabi-tag seem to be now generally unused
by everyone.
This fix is one step from many in process of porting package to
debian-stretch.
Mentioned GCC warning informs about situations where library may be theoretically successfully linked with another one built with incompatible ABI. For more info on this topic, see https://developers.redhat.com/blog/2015/02/05/gcc5-and-the-c11-abi/) https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html Unfortunately, the only way to make this warning disappear is explicitly put explicit abi_tag attribute to every single affected symbol, which seems excessive and does not help readibility. Notably, our internet research seem to suggest that this issue (linking code built with old and new ABI) is almost never occuring in practice, as all packages for given OS are by convention built with the same version. Judging from the relative lack of related problems, tutorials or general discussion about this topic, -Wabi-tag seem to be now generally unused by everyone.
This fix is one step from many in process of porting package to debian-stretch.