Bug 831776 – sys-fs/cryptsetup-2.4.3: libtool: warning: complete static linking is impossible in this configuration

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description dm9pZCAq 2022-01-22 08:45:22 UTC]

i'm trying to compile sys-fs/cryptsetup-2.4.3::gentoo with USE="-* argon2 nettle static"

and in the end of compilation is tells:
libtool: warning: complete static linking is impossible in this configuration

and `file /sbin/cryptsetup` tells that it is "dynamically linked"

Reproducible: Always

[Comment 1 Jonas Stein 2022-01-22 10:00:38 UTC]

Thank you for the report. We need to have all information at hand before ticket assignment. This includes
* the complete build.log as attachment and
* paste the emerge info 
as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket

Please reopen this ticket (Status:UNCONFIRMED) afterwards.

[Comment 2 dm9pZCAq 2022-01-22 15:06:51 UTC]

Created attachment 763251 [details]
build log

[Comment 3 dm9pZCAq 2022-01-22 15:08:37 UTC]

Created attachment 763253 [details]
emerge --info =sys-fs/cryptsetup-2.4.3

does this really matters?

i think you can reproduce this just with same USE flags

[Comment 4 Mike Gilbert 2022-01-22 15:24:07 UTC]

From your build log:

> checking if x86_64-gentoo-linux-musl-clang static flag -static works... no

That's quite strange. With a fully functional toolchain, it looks like this:

> checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes

Please attach config.log so we can see why this configure test is failing.

[Comment 5 Sam James 2022-01-22 15:31:46 UTC]

Globally setting -fPIC is a bad idea and will lead to various failures, even if it's not the issue here. We already set it by default.

(In reply to dm9pZCAq from comment #3)
> Created attachment 763253 [details]
> emerge --info =sys-fs/cryptsetup-2.4.3
> 
> does this really matters?
> 
> i think you can reproduce this just with same USE flags

With respect, I think this is a bit naive. Your setup is not simple or vanilla and even then, problems which seem easy to reproduce often can't. Happening for you doesn't mean it happens for us. Most bugs I fix are ones I fix based on information from users.

[Comment 6 dm9pZCAq 2022-01-22 16:31:11 UTC]

> With respect, I think this is a bit naive.

as it turned out, yes... sorry and thank you so much

problem was in -flto, i removed it and everything builds fine


> Globally setting -fPIC is a bad idea and will lead to various failures, even if it's not the issue here.

i never had problems with -fPIC, only some times with -fPIE