On Mon, Aug 10, 2015 at 16:28:51 +0200, Frank B. Brokken wrote:

> Dear Julien Cristau, you wrote:
> > Control: severity -1 serious
> > Control: tag -1 confirmed
> > 
> > On Tue, Jul  7, 2015 at 20:47:28 +0200, Frank B. Brokken wrote:
> > 
> > > >  - Rebuild the library using g++/g++-5 from experimental. Note that
> > > >    most likely all C++ libraries within the build dependencies need
> > > >    a rebuild too. You can find the log for a rebuild in
> > > >      https://people.debian.org/~doko/logs/gcc5-20150701/
> > > >    Search for "BEGIN GCC CXX11" in the log.
> > > > 
> > > >  - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
> > > >    library API, and are used by the reverse dependencies of the
> > > >    library.
> > > > 
> > [...]
> > > 
> > > Thx for the bug report. Right now I'm abroad, and unable to do any 
> > > maintenance
> > > until I'm back by the end of July. By then I'll have a close look at the
> > > points you're mentioning. 
> > > 
> > > Thanks again!
> > > 
> > Confirmed that public symbols are changing with the g++ 5 rebuild; a
> > patch to rename the library package is available at
> > https://launchpad.net/ubuntu/+source/bobcat/3.25.01-2ubuntu2
> 
> Thanks for the bug report. We're still working out how to handle this
> issue. The plan is to do an so bump to version 4 of the bobcat library. Some
> time ago (early August) Debian's experimental distro offered a g++ 5 release
> that indeed created a library in which the public symbols were changed. We
> think that bumping the so version, in line with an earlier e-mail by Matthias,
> effectively handlres the new symbols issue. However, by now the g++ 5 compiler
> no longer is available in Debian's experimental distribution, but only in
> Debian's stretch (testing) and sid(unstable) distros, and these compilers
> don't use the new naming conventions. Right now Tony and I are figuring out a
> strategy for handling this complication, but we're not done yet. This reaction
> is primarily to inform you that we're not ignoring the issue, but in fact are
> actively trying to find an adequate solution.
> 
You make it sound way more complicated than I believe it is...

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature

Reply via email to