[Debichem-devel] Bug#797293: Bug#797293: votca-csg: FTBFS: undefined reference to `votca::tools::RangeParser::Parse

[Christoph Junghans]

2015-09-02 1:46 GMT-06:00 Simon McVittie <smcv at debian.org>:
> Control: reassign 797293 votca-tools
> Control: found 797293 1.2.4-1
> Control: tag 797293 + sid stretch confirmed
> Control: affects 797293 votca-csg
> Control: retitle 797293 votca-tools: rename needed for libstdc++ ABI transition
> Control: user debian-gcc at lists.debian.org
> Control: usertags 797293 + libstdc++-cxx11
>
> On Sat, 29 Aug 2015 at 08:48:21 -0600, Christoph Junghans wrote:
>> 2015-08-29 3:45 GMT-06:00 Dominic Hargreaves <dom at earth.li>:
>> > CMakeFiles/csg_dump.dir/csg_dump.cc.o:(.data.rel.ro._ZTV10CsgDumpApp[_ZTV10CsgDu
>> > mpApp]+0x28): undefined reference to `votca::tools::Application::VersionString[a
>> > bi:cxx11]()'
>>
>> This is simple. votca-tools, the prime dependency of votca-csg, was
>> compiled with a compiler with a different cxx11 abi, you will need to
>> re-compile votca-tools with same compiler.
>
> This implies that votca-tools needs an ABI transition.
>
> 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,
> 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.
>
> In the case of votca-tools, Dominic's bug report indicates that a transition
> is definitely required. The transition consists of renaming the affected
> library packages, adding a v5 suffix (libgdcm2.4v5, etc.). The SONAME
> should not be changed.
I currently don't have a debian development system handy, but is there
anything I can do from the upstream side?

>
> These follow-up transitions for libstdc++ are not going through exactly
> the normal transition procedure, because many entangled transitions are
> going on at the same time, and the usual ordered transition procedure
> does not scale that far. When all the C++ libraries on which this library
> depends have started their transitions in unstable if required, this
> library should do the same, closing this bug; the release team will deal
> with binNMUs as needed.
>
> In the case of votca-tools:
>
> * boost has already started its transition
> * the other library build-deps appear to have C ABIs
>
> so I think this is ready to go.
>
> The package is likely to be NMU'd if there is no maintainer response. The
> release team have declared a 2 day NMU delay[2] for packages involved
> in the libstdc++ transition, in order to get unstable back to a usable
> state in a finite time.
>
> Regards,
>     S
>
> [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
> [2] https://lists.debian.org/debian-devel-announce/2015/08/msg00000.html



-- 
Christoph Junghans
Web: http://www.compphys.de