> So it looks like the canonical reference for this issue is going to be "GCC5 > and the C++11 ABI", > https://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/. > > <SNIP> > Many users routinely rebuild all their code when they change compilers; such > users will be unaffected by this change. Code built with an earlier compiler > will also continue to work with the new libstdc++, which provides both old > and new ABIs. > > Users that depend on third-party libraries or plugin interfaces that still > use the old ABI can build their code with -D_GLIBCXX_USE_CXX11_ABI=0 and > everything should work fine. In most cases, it will be obvious when this > flag is needed because of errors from the linker complaining about > unresolved symbols involving “__cxx11”. > > Providers of such libraries or interfaces need to consider whether they want > to provide ABI coexistence, like libstdc++ does, or require their users to > rebuild. If they want to provide coexistence, they need to understand how > to handle the change. > </SNIP> > > I'm going to attempt the "coexist thing" mentioned in the post. If > successful, then maybe we can get Debian and Fedora to build us with it.
According to one of the GCC devs, its currently not possible to obtain coexistence and have things work for Clang (if I am parsing it correctly). Also see "How to provide coexisting std::string's (with and without abi:cxx11) in GCC 5.1 and above", https://gcc.gnu.org/ml/gcc-help/2016-03/msg00118.html. I'm not sure what we can do here. Very frustrating.... Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
