Bug#583387: closed by Bastian Blank <waldi at debian.org> (Re: Bug#583387: no longer shipping static libraries causes cryptsetup FTBFS)

[Jonas Meurer]

hey,

On 27/05/2010 Bastian Blank wrote:
> On Thu, May 27, 2010 at 07:13:01PM +0200, Jonas Meurer wrote:
> > but still the most recent update of libdevmapper broke cryptsetup build.
> > see the build logs at https://buildd.debian.org/pkg.cgi?pkg=cryptsetup:
> 
> > make[3]: Entering directory `/build/buildd-cryptsetup_1.1.1-1-i386-X7Uy0C/cryptsetup-1.1.1/src'
> > gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../lib -DDATADIR=\""/usr/share"\" -DLOCALEDIR=\""/usr/share/locale"\" -DLIBDIR=\""/usr/lib"\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/usr/etc"\" -DVERSION=\""1.1.1"\" -D_GNU_SOURCE   -Wall -Wall -g -O2 -MT cryptsetup-cryptsetup.o -MD -MP -MF .deps/cryptsetup-cryptsetup.Tpo -c -o cryptsetup-cryptsetup.o `test -f 'cryptsetup.c' || echo './'`cryptsetup.c
> > mv -f .deps/cryptsetup-cryptsetup.Tpo .deps/cryptsetup-cryptsetup.Po
> > /bin/sh ../libtool --tag=CC   --mode=link gcc -Wall -Wall -g -O2 -all-static  -o cryptsetup cryptsetup-cryptsetup.o ../lib/libcryptsetup.la -lgcrypt -lgpg-error -lselinux -lsepol  -lpopt  
> > libtool: link: gcc -Wall -Wall -g -O2 -static -o cryptsetup cryptsetup-cryptsetup.o  ../lib/.libs/libcryptsetup.a -luuid -L/lib -ldevmapper -lpthread /usr/lib/libgcrypt.a /usr/lib/libgpg-error.a -lselinux -lsepol /usr/lib/libpopt.a
> > /usr/bin/ld: cannot find -ldevmapper
> > collect2: ld returned 1 exit status
> > make[3]: *** [cryptsetup] Error 1
> > make[3]: Leaving directory `/build/buildd-cryptsetup_1.1.1-1-i386-X7Uy0C/cryptsetup-1.1.1/src'
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory `/build/buildd-cryptsetup_1.1.1-1-i386-X7Uy0C/cryptsetup-1.1.1'
> > make[1]: *** [all] Error 2
> > make[1]: Leaving directory `/build/buildd-cryptsetup_1.1.1-1-i386-X7Uy0C/cryptsetup-1.1.1'
> > make: *** [build-stamp] Error 2
> > dpkg-buildpackage: error: debian/rules build gave error exit status 2
> > 
> > i can reproduce this bug with libdevmapper-dev 2:1.02.47-1.
> 
> This is not the same version then already in unstable. So you can't even
> show on which side it break. As you link with -static, it will only
> consider static libs.

yes, this is the most recent devmapper version in unstable. at least it
is the one available at packages.debian.org, on my local system, and
being used on the buildds:

https://buildd.debian.org/fetch.cgi?pkg=cryptsetup;ver=2%3A1.1.1-1;arch=i386;stamp=1274915533
> Selecting previously deselected package libdevmapper1.02.1.
> Unpacking libdevmapper1.02.1 (from .../libdevmapper1.02.1_2%3a1.02.47-1_i386.deb) ...
> [...]
> Selecting previously deselected package libdevmapper-dev.
> Unpacking libdevmapper-dev (from .../libdevmapper-dev_2%3a1.02.47-1_i386.deb) ...
> [...]
> Setting up libdevmapper1.02.1 (2:1.02.47-1) ...
> [...]
> Setting up libdevmapper-dev (2:1.02.47-1) ...

> However the question is: why did it build on your system for the initial
> upload. Out-of-date system?

yes, i missed to update my pbuilder environment before building
cryptsetup, thus it used old libdevmapper. from local build-log:

> Selecting previously deselected package libdevmapper-dev.
> Unpacking libdevmapper-dev (from .../libdevmapper-dev_2%3a1.02.45-1_amd64.deb) ...
> [...]
> Setting up libdevmapper-dev (2:1.02.45-1) ...

i just rechecked, and the now up-to-date pbuilder environment fails to
build cryptsetup, while after downgrading libdevmapper1.02.1 and
libdevmapper-dev the packages build fine. so it's definitely connected
to the devmapper package upgrade.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20100527/5836d34c/attachment.pgp>