Quoting Andreas Tille (2016-07-20 16:27:08) > On Wed, Jul 20, 2016 at 01:58:18PM +0200, Jonas Smedegaard wrote: > > 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. > > 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. > > I think I found the cause of the issue (I intentionally do not write > bug). The thing is that wildcards seem to confuse d-shlibmove. If I > specify all single *.a libs that are needed to be moved d-shlibmove > works fine (see commit 66ce4e9a7404cee9e06f24cbf97c45db48c707d5). [details snipped] > So d-shlibmove interprets the last match of the wildcard expression as > shared library name (which is obviosly not in this case). Since I > found a solution for this package and I'm not really sure I'll leave > it to your decision whether this should be considered a bug and should > be closed or whether you close the bug report.
Ahh - yes, d-shlibs "--movedev" option expects exactly two arguments (unlike common for dh_* tools) - as documented in its manpage: --movedev [filename] [relative dir-path] Further "arguments" are seen not as belonging to that option but the library path, as per its manpage: d-shlibmove [options] shared-library.so I will therefore say that there is at best a wishlist bug to change logic of argument parsing. That does make some sense - I will leave it to you to decide if you want this bugreport repurposed for that or not. - 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
