Here also a discussion about the problem on the gcc mailing list
https://gcc.gnu.org/ml/gcc-help/2015-09/msg00057.html
It seems that a abi_tag attribut should be added in tango to the problematic
symbols in order to help gcc5 decide which ABI is expected.
ifdef _GLIBCXX_USE_CXX11_ABI
define TAN
I started a thread about this on debian-python mailing list.
https://lists.debian.org/debian-python/2015/09/msg00028.html
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintaine
:/usr/lib/i386-linux-gnu$ nm -D libtango.so.8.1.2 | grep ranges_type | c++filt
0045f258 D Tango::ranges_type2const::enu
00460dfc B Tango::ranges_type2const::str[abi:cxx11]
0045f280 D Tango::ranges_type2const::enu
00460fdc B Tango::ranges_type2const::str[abi:cxx11]
0045f27c D Tango::ranges_type2co
