I've a 32 bit chroot on an amd64 gentoo (testing), I was trying to install crypsetup, but the configure failed with "configure: error: 'You need the device-mapper library'". Downgrading lvm2 to the old version (2.02.56-r3) solved the issue. Reproducible: Always
Post the config.log from cryptsetup along with your emerge --info
Created attachment 228671 [details] emerge --info of the 32 bit chroot
Created attachment 228673 [details] cryptsetup configure log
*** Bug 316591 has been marked as a duplicate of this bug. ***
configure:14431: checking for dm_task_set_name in -ldevmapper configure:14456: i686-pc-linux-gnu-gcc -o conftest -march=core2 -O2 -pipe -Wl,-O1 conftest.c -ldevmapper >&5 /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/../../../../i686-pc-linux-gnu/bin/ld: cannot open linker script file /lib/libdevmapper.so: No such file or directory collect2: ld returned 1 exit status
reproduced, will fix tmrw
*** Bug 316689 has been marked as a duplicate of this bug. ***
*** Bug 316705 has been marked as a duplicate of this bug. ***
Ok, please test lvm2-2.02.63-r2 that I've just added to the tree.
Hmm.. I run emerge --sync but there is no lvm2-2.02.63-r2.. s0uRg3 n3ph # emerge -s lvm2 Searching... [ Results for search key : lvm2 ] [ Applications found : 1 ] * sys-fs/lvm2 Latest version available: 2.02.63-r1 Latest version installed: 2.02.56-r3 Size of files: 842 kB Homepage: http://sources.redhat.com/lvm2/ Description: User-land utilities for LVM2 (device-mapper) software. License: GPL-2 did you mean you added it to an overlay or to the main-portage?? n3ph
Nope, you just need to wait a little longer, here's my buffer from earlier. Using commit message: ------------------------------------------------------------------------------ Bug #316571: more work on library installs. (Portage version: 2.2_rc67/cvs/Linux x86_64) ------------------------------------------------------------------------------ /var/cvsroot/gentoo-x86/sys-fs/lvm2/ChangeLog,v <-- ChangeLog new revision: 1.205; previous revision: 1.204 /var/cvsroot/gentoo-x86/sys-fs/lvm2/lvm2-2.02.63-r2.ebuild,v <-- lvm2-2.02.63-r2.ebuild initial revision: 1.1 >>> Creating Manifest for /usr/portage/sys-fs/lvm2 /var/cvsroot/gentoo-x86/sys-fs/lvm2/Manifest,v <-- Manifest new revision: 1.250; previous revision: 1.249 Commit complete. RepoMan sez: "If everyone were like you, I'd be out of business!"
how long does it usually take for committed ebuilds to be synced on repos?
15-60 minutes depending on which of the mirrors you're hitting (official vs. community). If you're using an additional custom tier beyond that, possibly longer. I've got an ACK on this working now too.
Created attachment 228833 [details] build log of sys-fs/cryptsetup-1.1.0
hm :) too few information , i was so tired last night that i just uploaded the build-log from cryptsetup... please REOPEN... I compiled lvm2-2.02.63-r2 successfully.. Compilation of cryptsetup-1.1.0 against the new libdevmapper.a failed -> see build.log
*** Bug 316793 has been marked as a duplicate of this bug. ***
Reopen per Comment #14 and bug 316793.
Created attachment 228901 [details] cryptsetup-1.1.0 build.log after upgrading to lvm2-2.02.63-r2 It gets past the configurescript now but still fails due to devmapper during the compile.
Dakota: Does your udev have /usr/lib/libudev.a and /usr/lib/libudev.so? I don't see them being referenced at all from the linking call to gcc.
(In reply to comment #19) > Dakota: > Does your udev have /usr/lib/libudev.a and /usr/lib/libudev.so? > I don't see them being referenced at all from the linking call to gcc. > Sure does. I'm using udev-151-r2
*** Bug 316839 has been marked as a duplicate of this bug. ***
Created attachment 228919 [details, diff] cryptsetup-1.1.0-udev.patch Well, here is a patch against cryptsetup-1.1.0 to link against -ludev. It basically checks if udev is present and then feeds the -ludev to linker... I'm sure there are better ways to accomplish the same, but this works for me
ssuominen: Ok, committed that patch now. We should encourage cryptsetup upstream to move to pkgconfig for libdevmapper, as that will bring in the libudev too.
(In reply to comment #23) > ssuominen: > Ok, committed that patch now. We should encourage cryptsetup upstream to move > to pkgconfig for libdevmapper, as that will bring in the libudev too. > nod, I've opened a upstream bug for this, the problem is pretty clear but as usual I suck at explaining myself so if you have something to add... please do http://code.google.com/p/cryptsetup/issues/detail?id=64
A work-around exists by adding "dynamic" use flag. This will allow a successful build to complete. http://forums.gentoo.org/viewtopic-t-824816.html
(In reply to comment #25) > A work-around exists by adding "dynamic" use flag. > This will allow a successful build to complete. > http://forums.gentoo.org/viewtopic-t-824816.html You don't need that. Just sync and get the updated ebuild with the patch. Re the libdevmapper pkgconfig, upstream LVM says that will be in .64, along with other library cleanups.
artie: please CC yourself if you're going to be getting a response. see my comment #26.
*** Bug 316873 has been marked as a duplicate of this bug. ***
*** Bug 324141 has been marked as a duplicate of this bug. ***
Hi, just to say that i had the pb on stable amd64 system with cryptsetup added to package.keywords It seems like old udev ebuilds do not build and/or install the static libudev.a, only newer ebuilds. And recent cryptsetup packages rely on this static lib being available. By unmasking udev as well, i've solved my pb and could install cryptsetup. (equery files mention libudev.a now)
