trying to solve the pytango FTBFS with gcc5

2015-09-06 Thread PICCA Frederic-Emmanuel
Hello, guyes, I am working on this bug report[1], and I would like your opinion. this package depends on the tango library which was rebuilt with gcc5 and updated for the libstdc++6 transition. Now as you can see in the bug report, pytango FTBFS with a missing symbol. and indeed the missing symb

Re: trying to solve the pytango FTBFS with gcc5

2015-09-06 Thread Scott Kitterman
On Sunday, September 06, 2015 08:23:37 AM PICCA Frederic-Emmanuel wrote: > Hello, guyes, > > I am working on this bug report[1], and I would like your opinion. > this package depends on the tango library which was rebuilt with gcc5 and > updated for the libstdc++6 transition. > > Now as you can s

Re: trying to solve the pytango FTBFS with gcc5

2015-09-06 Thread Matthias Klose
On 09/06/2015 04:24 PM, Scott Kitterman wrote: > On Sunday, September 06, 2015 08:23:37 AM PICCA Frederic-Emmanuel wrote: >> Hello, guyes, >> >> I am working on this bug report[1], and I would like your opinion. >> this package depends on the tango library which was rebuilt with gcc5 and >> updated

Re: trying to solve the pytango FTBFS with gcc5

2015-09-06 Thread Dmitry Shachnev
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 > _ZN5Tango11Devic

Re: trying to solve the pytango FTBFS with gcc5

2015-09-06 Thread Dmitry Shachnev
On Sun, 06 Sep 2015 18:28:04 +0300, Dmitry Shachnev wrote: > 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

RE:trying to solve the pytango FTBFS with gcc5

2015-09-06 Thread PICCA Frederic-Emmanuel
> 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 pro

RE:trying to solve the pytango FTBFS with gcc5

2015-09-06 Thread PICCA Frederic-Emmanuel
> I have created a small test project (attached) that has a library exporting > "std::string Tango::ranges_type2const::str" symbol and a test program > using it. thanks a lot. now we can see if gcc and g++ generate different symbols. > Interestingly, GCC uses the symbol _ZN5Tango17ranges_type2c

RE:trying to solve the pytango FTBFS with gcc5

2015-09-06 Thread PICCA Frederic-Emmanuel
> I have created a small test project (attached) that has a library exporting > "std::string Tango::ranges_type2const::str" symbol and a test program > using it. > Interestingly, GCC uses the symbol _ZN5Tango17ranges_type2constIjE3strE > (*without* the B5cxx11 part) for both library and client. Y

RFS: python-httplib2 -- fix of #794750

2015-09-06 Thread Ilias Tsitsimpis
Hello team, The latest version of the python-oauth2client package depends on httplib2 (>=0.9.1), but the current version of python-httplib2 on Debian is 0.9 [#794312]. This makes Python applications that depends on python-oauth2client (such as goobook [#797068]) break. Although I agree that this