I disabled lto, but it comes back in via <foo>-config --libs

[Steve Langasek]

Hi Andreas,

On Fri, Apr 29, 2022 at 10:50:21AM -0300, Andreas Hasenack wrote:
> I disabled lto in a build according to the instructions from [1]:

> export DEB_BUILD_MAINT_OPTIONS=optimize=-lto

> But I saw that it was still present in some steps of the build.
> Notably when krb5/gssapi was used:

[...]

> That sounds bad. It means only portions of the build will have lto
> disabled, while others will flip it back on. How to sort this out?
> Looks like the krb5 package needs some fixing, but I'm unsure how.

I think your main question has been addressed.  But I want to ask, why is it a
problem to have part of this code with LTO enabled?  Generally we disable
LTO only when it is causing build failures.  Was that the case here?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                   https://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20220429/0eb11209/attachment.sig>