546894 – sys-fs/cryptsetup-1.6.7: cannot emerge a static binary

Bug 546894 - sys-fs/cryptsetup-1.6.7: cannot emerge a static binary

Summary: sys-fs/cryptsetup-1.6.7: cannot emerge a static binary

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-04-17 09:34 UTC by qdii
Modified:	2015-04-23 17:18 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Log from emerge -NuD lvm2 cryptsetup (emerge.log,350.85 KB, text/plain) 2015-04-17 09:34 UTC, qdii	Details
emerge --info cryptsetup (emerge.info,5.89 KB, text/plain) 2015-04-17 09:35 UTC, qdii	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description qdii 2015-04-17 09:34:03 UTC

Created attachment 401444 [details]
Log from emerge -NuD lvm2 cryptsetup

This is from a fresh install.

Steps to reproduce:
1. modify USE flags to force a static build:
echo "sys-fs/cryptsetup static -dynamic static-libs" >> /etc/portage/package.use/cryptsetup
echo "sys-fs/lvm2 static -dynamic static-libs" >> /etc/portage/package.use/lvm2

2. emerge both packages:
emerge -NuD lvm2 cryptsetup

3. notice that cryptsetup are dynamically link to shared objects:
ldd /sbin/cryptsetup
        …
        libattr.so.1 => /lib64/libattr.so.1 (0x00007fd96603c000)
        libcryptsetup.so.4 => …


Expected result:
/sbin/cryptsetup should not depend on any shared object

I need a static binary for my initramfs.

Comment 1 qdii 2015-04-17 09:35:06 UTC

Created attachment 401446 [details]
emerge --info cryptsetup

Comment 2 Mike Gilbert gentoo-dev

2015-04-23 17:18:19 UTC

You are using a systemd profile, which masks the "static" and "static-libs" use flags.