On Sun, 6 Sep 2015 16:35:40 +0200, Matthias Klose wrote: >> The old abi is explicitly set by line 261 of setup.py. > > no. the libstdc++ ABI is unrelated to the C++ standard used for the build. > > the symbol is defined: > > $ objdump -T /usr/lib/x86_64-linux-gnu/libtango.so|grep > _ZN5Tango11DeviceProxy14get_corba_nameB5cxx11Eb > 00000000002ce1a0 g DF .text 0000000000000388 Base > _ZN5Tango11DeviceProxy14get_corba_nameB5cxx11Eb > > so find out why _PyTango.so doesn't find it. The actual error is about another symbol: _PyTango.so: undefined symbol: _ZN5Tango17ranges_type2constIjE3strE This symbol is old ABI, as opposed to _ZN5Tango17ranges_type2constIjE3strB5cxx11E (which *does* exist in libtango.so.8). Can it be a bug in GCC? I don't think it should produce such a broken _PyTango.so. -- Dmitry Shachnev
Attachment:
signature.asc
Description: OpenPGP digital signature