View previous topic :: View next topic |
Author |
Message |
o5gmmob8 Guru
Joined: 17 Oct 2003 Posts: 465
|
Posted: Sat Jul 07, 2012 3:21 pm Post subject: cannot build cryptsetup statically for encrypted root |
|
|
Hi all,
I am attempting to install / build cryptsetup with the static use flag, but cannot. It appears it is looking for udev at a certain location and is not finding it?
Code: |
/usr/lib/gcc/i686-pc-linux-gnu/4.6.2/../../../../lib/libdevmapper.a(libdm-common.o): In function `_check_udev_sync_requirements_once':
(.text+0x107f): undefined reference to `udev_new'
/usr/lib/gcc/i686-pc-linux-gnu/4.6.2/../../../../lib/libdevmapper.a(libdm-common.o): In function `_check_udev_sync_requirements_once':
(.text+0x1091): undefined reference to `udev_queue_new'
/usr/lib/gcc/i686-pc-linux-gnu/4.6.2/../../../../lib/libdevmapper.a(libdm-common.o): In function `_check_udev_sync_requirements_once':
(.text+0x10a3): undefined reference to `udev_queue_get_udev_is_active'
/usr/lib/gcc/i686-pc-linux-gnu/4.6.2/../../../../lib/libdevmapper.a(libdm-common.o): In function `_check_udev_sync_requirements_once':
(.text+0x10b1): undefined reference to `udev_queue_unref'
/usr/lib/gcc/i686-pc-linux-gnu/4.6.2/../../../../lib/libdevmapper.a(libdm-common.o): In function `_check_udev_sync_requirements_once':
(.text+0x10b9): undefined reference to `udev_unref'
/usr/lib/gcc/i686-pc-linux-gnu/4.6.2/../../../../lib/libdevmapper.a(libdm-common.o): In function `_check_udev_sync_requirements_once':
(.text+0x11eb): undefined reference to `udev_unref'
collect2: ld returned 1 exit status
make[2]: *** [cryptsetup.static] Error 1
make[2]: Leaving directory `/var/tmp/portage/sys-fs/cryptsetup-1.4.3/work/cryptsetup-1.4.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/sys-fs/cryptsetup-1.4.3/work/cryptsetup-1.4.3'
make: *** [all] Error 2
* ERROR: sys-fs/cryptsetup-1.4.3 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=sys-fs/cryptsetup-1.4.3'`,
* the complete build log and the output of `emerge -pqv '=sys-fs/cryptsetup-1.4.3'`.
* The complete build log is located at '/var/tmp/portage/sys-fs/cryptsetup-1.4.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-fs/cryptsetup-1.4.3/temp/environment'.
* Working directory: '/var/tmp/portage/sys-fs/cryptsetup-1.4.3/work/cryptsetup-1.4.3'
* S: '/var/tmp/portage/sys-fs/cryptsetup-1.4.3/work/cryptsetup-1.4.3'
>>> Failed to emerge sys-fs/cryptsetup-1.4.3, Log file:
>>> '/var/tmp/portage/sys-fs/cryptsetup-1.4.3/temp/build.log'
* Messages for package sys-fs/cryptsetup-1.4.3:
* This profile has not been tested thoroughly and is not considered to be
* a supported server profile at this time. For a supported server
* profile, please check the Hardened project (http://hardened.gentoo.org).
* This profile is merely a convenience for people who require a more
* minimal profile, yet are unable to use hardened due to restrictions in
* the software being used on the server. This profile should also be used
* if you require GCC 4.1 or Glibc 2.4 support. If you don't know if this
* applies to you, then it doesn't and you should probably be using
* Hardened, instead.
* ERROR: sys-fs/cryptsetup-1.4.3 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=sys-fs/cryptsetup-1.4.3'`,
* the complete build log and the output of `emerge -pqv '=sys-fs/cryptsetup-1.4.3'`.
* The complete build log is located at '/var/tmp/portage/sys-fs/cryptsetup-1.4.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-fs/cryptsetup-1.4.3/temp/environment'.
* Working directory: '/var/tmp/portage/sys-fs/cryptsetup-1.4.3/work/cryptsetup-1.4.3'
* S: '/var/tmp/portage/sys-fs/cryptsetup-1.4.3/work/cryptsetup-1.4.3'
|
Any ideas as to what I should check? Also, I don't believe it makes a difference, but I am using Funtoo.
Walter |
|
Back to top |
|
|
olek Apprentice
Joined: 22 Oct 2011 Posts: 173
|
Posted: Sun Jul 08, 2012 6:55 pm Post subject: |
|
|
Is udev built with USE=static-libs ? _________________ https://plaintext.blog |
|
Back to top |
|
|
o5gmmob8 Guru
Joined: 17 Oct 2003 Posts: 465
|
Posted: Sun Jul 08, 2012 9:20 pm Post subject: |
|
|
Hi,
Thanks for your reply, but udev doesn't have that option, at least for me. That was the first thing I checked, I'll check again though more thoroughly.
Code: |
sys-fs/udev-171-r6 USE="acl gudev hwdb -extras -introspection (-selinux)"
|
Walter |
|
Back to top |
|
|
kiwi-kiwi n00b
Joined: 18 Jul 2012 Posts: 1
|
Posted: Wed Jul 18, 2012 11:20 pm Post subject: |
|
|
Hi,
i went in the same problem. It seems that there is a problem with the lvm-version 2.02.88. So the fix for me was to mask this version and recompile lvm.
Code: | echo "=sys-fs/lvm2-2.02.88" >> /etc/portage/package.mask |
After that the compilation of cryptsetup went fine.
Cheers,
kiwi |
|
Back to top |
|
|
o5gmmob8 Guru
Joined: 17 Oct 2003 Posts: 465
|
Posted: Thu Jul 19, 2012 11:48 am Post subject: |
|
|
Hi,
Thanks for your reply, I will give that a try and report back.
Walter |
|
Back to top |
|
|
o5gmmob8 Guru
Joined: 17 Oct 2003 Posts: 465
|
Posted: Fri Jul 20, 2012 11:00 am Post subject: [solved] |
|
|
Hi,
I think that did it, it appears genkernel is now adding in support for luks.
Thanks again,
Walter |
|
Back to top |
|
|
o5gmmob8 Guru
Joined: 17 Oct 2003 Posts: 465
|
Posted: Sat Jul 21, 2012 5:10 am Post subject: [solved] |
|
|
Hi,
Thanks again for your help. I was able to boot up okay, well kinda. I had to use the shell to enter the path to the encrypted root device, although I thought I had entered on the grub configuration. What key/value pairs should I be using as my configuration appears invalid?
Code: |
dolvm crypt_root=/dev/sda2 real_root=/dev/mapper/40GB-gentoo--root rootfstype=ext4
|
Other than that, I am happy to be back to gentoo for the speed and snappiness, hopefully I will figure out some sort of stable, ease of maintenance thing.
Thanks,
Walter |
|
Back to top |
|
|
Sacha_D n00b
Joined: 20 Dec 2017 Posts: 2
|
Posted: Wed Dec 20, 2017 3:56 pm Post subject: |
|
|
I have the same problem, when I trying to emerge sys-boot/grub or sys-boot/lilo. sys-fs/lvm2 is 2.02.145-r2. What should I do? Thank you. |
|
Back to top |
|
|
Sacha_D n00b
Joined: 20 Dec 2017 Posts: 2
|
Posted: Wed Dec 20, 2017 7:47 pm Post subject: |
|
|
I disabled static USE flag -static. And it was emerged. |
|
Back to top |
|
|
|