Quoting Andreas Tille (2016-07-20 13:06:05) > when trying to build ncbi-vdb[1] which has an admittedly hard to > understand self-made build system I end up with > > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib/*.a > usr/lib/x86_64-linux-gnu \ > --movedev interfaces/ngs/ncbi/NGS.hpp usr/include/ncbi-vdb \ > debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib/libncbi-vdb.so > Library package automatic movement utility > /usr/bin/d-shlibmove: > [debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib/libncbi-vdb.a] is not a > valid shared library file name > debian/rules:43: recipe for target 'override_dh_auto_install' failed > > > I agree that *.a is no valid shared library file name - but why does > d-shlibmove assume this is regarded as a shared lib? > > Jonas suggested to discuss this in BTS and so here is the according > bug.
Thanks! I honestly don't know if d-shlibs has spotted an issue with how the library linkage is done, or you've revealed a bug in d-shlibs. Next step is probably to look closer at what d-shlibs did (e.g. with "bash -x ..." or simply close-reading the code), and compare that to Debian Policy or other sources of how linkage hints are supposed to behave regarding stating libraries. Will you have the honour? > The build happended in an unstable pbuilder chroot - so the system > information below is irrelevant. For the future: Simply strip irrelevant parts before sending the bugreport. :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
