SF Markus Elfring
3. Make mangling style part of library Provides and Requires.
How are the chances to reduce surprises from name mangling by such an approach? How often were similar attempts discussed already?
The third one sounds feasible, something like
Requires: liby2.so.4(stdc++11)
assuming it is possible to detect how library was built.
Would you like to introduce dedicated variables?
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]() Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org