Bug 409039 – sys-fs/cryptsetup-1.4.1[static] fails to build against sys-fs/udev-182

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description jannis 2012-03-20 17:25:25 UTC]

I upgraded udev from 171-r5 to 182 and now cryptsetup fails with:
/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -ludev

I emerged cryptsetup using: USE="static static-libs" emerge -1av cryptsetup since I want to use it in an initramfs. However, I don't have static or static-libs in my make.conf (see emerge --info)

Just verified again: cryptsetup build fine after downgrading udev to 171-r5

Reproducible: Always

[Comment 1 jannis 2012-03-20 17:25:46 UTC]

Created attachment 306021 [details]
build.log

[Comment 2 jannis 2012-03-20 17:26:43 UTC]

Created attachment 306023 [details]
equery f udev (with udev-182 installed)

[Comment 3 jannis 2012-03-20 17:28:55 UTC]

Created attachment 306025 [details]
emerge --info

[Comment 4 Samuli Suominen (RETIRED) 2012-03-20 17:32:02 UTC]

If you emerge sys-fs/udev with USE="static-libs" you should get this file:

sys-fs/udev-182 (/usr/lib/libudev.a)

You don't have it? Post 'emerge -pv sys-fs/udev'

[Comment 5 jannis 2012-03-20 17:34:15 UTC]

Yes, you're right. It just came to my mind that I'll have to built udev with +static, too. Propably is RESOLVED INVALID.

Is a system-wide +static +static-libs the preferred way?

[Comment 6 jannis 2012-03-20 17:36:41 UTC]

Or better: is it possible to install the .a-file even if I emerge udev with -static?

[Comment 7 Samuli Suominen (RETIRED) 2012-03-20 17:37:36 UTC]

nevermind, it was simple as missing dependency since USE=static-libs is new for udev since 182:

+  20 Mar 2012; Samuli Suominen <[e-mail]>
+  cryptsetup-1.2.0-r1.ebuild, cryptsetup-1.4.1.ebuild:
+  Make sure sys-fs/udev has been emerged with USE="static-libs" for
+  USE="static" wrt #409039 by jannis

[Comment 8 Samuli Suominen (RETIRED) 2012-03-20 17:39:49 UTC]

(In reply to comment #5)
> Is a system-wide +static +static-libs the preferred way?

absolutely not, try to stay away from USE=static and USE=static-libs much as possible
setting USE=static system-wide can potentially break your system at some point and USE=static-libs will just double your system size by installing a lot of unnecessary .a files

[Comment 9 jannis 2012-03-20 17:46:44 UTC]

(In reply to comment #8)
> (In reply to comment #5)
> > Is a system-wide +static +static-libs the preferred way?
> 
> absolutely not, try to stay away from USE=static and USE=static-libs much as
> possible
> setting USE=static system-wide can potentially break your system at some
> point and USE=static-libs will just double your system size by installing a
> lot of unnecessary .a files

Okay, that was what I thought. Thanks for fixing :)

[Comment 10 jannis 2012-03-20 17:47:29 UTC]

ops :)