Re: [opensuse-packaging] Re: How to avoid more undefined symbols?

Hi, On Mon, 13 Jul 2015, Andreas Schwab wrote:

...

...

I do not know if this information is stored in library though.

It will finally land in special function names, won't it?

It will show up in the demangled symbol as "[abi:cxx11]".

$ c++filt _ZN6LHAPDF5pathsB5cxx11Ev LHAPDF::paths[abi:cxx11]()

Not for all of them: $ c++filt \ _ZN9libmodman14module_manager8load_dirENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEb libmodman::module_manager::load_dir(std::__cxx11::basic_string, bool) (That's the symbol Markus initially stumbled over) Here the only indication is the __cxx11 namespace before basic_string, which is a good hint (but not all __cxx11 occurrences mean an ABI change). Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org