Control: severity -1 serious Control: tag -1 confirmed On Fri, Jul 3, 2015 at 13:10:42 +0000, Matthias Klose wrote:
> Background [1]: libstdc++6 introduces a new ABI to conform to the > C++11 standard, but keeps the old ABI to not break existing binaries. > Packages which are built with g++-5 from experimental (not the one > from testing/unstable) are using the new ABI. Libraries built from > this source package export some of the new __cxx11 or B5cxx11 symbols, > and dropping other symbols. If these symbols are part of the API of > the library, then this rebuild with g++-5 will trigger a transition > for the library. > > What is needed: > > - 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. > From the log and the public headers of the package, it does look like the libraries shipped by jags break ABI on a rebuild with the new libstdc++. However, instead of being properly split out as required by policy, the libraries are shipped as part of the 'jags' binary package, which makes this a bit of a pain. I guess what needs to happen now is - split the libraries out to separate binary packages - add Breaks on r-cran-rjags (<< 1:3-15-1) (thankfully the only reverse dependency) - rebuild r-cran-rjags Cheers, Julien
signature.asc
Description: Digital signature
