[Debian-med-packaging] Bug#907358: ncbi-vdb: fix broken library on i386

Andreas Tille andreas at an3as.eu
Tue Aug 28 20:38:50 BST 2018


Control: tags -1 help

Hi Steve,

On Sun, Aug 26, 2018 at 03:04:40PM -0700, Steve Langasek wrote:
> Package: ncbi-vdb
> Version: 2.9.1-1+dfsg-1
> Severity: grave
> Tags: patch
> User: ubuntu-devel at lists.ubuntu.com
> Usertags: origin-ubuntu cosmic ubuntu-patch
> 
> Dear Andreas,
> 
> The libncbi-vdb2 library is broken on i386, because while it has managed to
> build, it has unresolvable references:
> ...
> It would also be perfectly reasonable to drop i386 as a supported
> architecture for ncbi-vdb if you prefer; but I suggest you then make sure to
> actually do this, rather than shipping a broken library package on i386.

Thanks to your patch I decided to leave i386 for the moment but its
definitely a candidate for removal.

> Also, this broken library package would have been detectable at build time
> if you were building with -Wl,-z,defs in LDFLAGS, as that would have
> prevented ever generating a shared library with missing symbols.  That's a
> good idea to do anyway, but in particular it would mean that if you didn't
> want to support i386 anymore, you could just add this to build flags and not
> have to worry about changing the architecture list explicitly.

So I did but was running into new problems which are caused by the hand
craftet build system (yes, I tried to convince upstream to use some of
the usual candidates but failed :-((( ).  I was able to add some missing
libs in pbuilder chroot but whatever trick I try[1] the build system
always constructs a different command line than I tested inside the
pbuilder chroot.

Do you have any idea to stop this insane messing up with library options?


[1] https://salsa.debian.org/med-team/ncbi-vdb/blob/master/debian/patches/fix_linking.patch

-- 
http://fam-tille.de



More information about the Debian-med-packaging mailing list