> 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. Yes I have this feeling also. I do not understand why gcc produce something with the old ABI. Except thaht python build extensions with gcc and not g++. Maybe this is the problem. gcc and g++ do not behave the same when compiling c++ files ? Fred
