[Bug 51051] Build fails when LTO is enabled

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51051

--- Comment #15 from Sveinar Søpler <cybermax at dexter.no> ---
(In reply to Rosanne DiMesio from comment #14)
> (In reply to Sveinar Søpler from comment #13)
> > 
> > Did you try to do a standalone build on hirsute? outside of debbuild i mean?
> > 
> 
> I only build the packages on the OBS, and for myself, making that work is
> all I am concerned about. As I said in comment #2, I have accomplished that
> by disabling LTO in the rules file, so my problem is solved. The reason I
> asked about configure is because this has been done in the past for other
> problematic distro package-building defaults that were also easily handled
> by changes to the build scripts (e.g., fortify, fcf-protection). That's for
> the developers to decide.
> 
> This is definitely not an issue unique to hirsute, because LTO has to be
> disabled to build Fedora and openSUSE packages.

But is not that the "normal way" to build distro packages? Distro-spesific
customizations when building packages?

If a regular configure && make build of wine would not work - as i would
venture a guess is the case for fcf-protection maybe - i would agree, but it
seems to be the "package building software" that is causing this -flto flag
usage (and the need for LTO exclusion list, since that would not work when
building it yourself anyway). 

If you actually had to specify -fno-lto to configure when building manually on
21.04 (or others), i can see that being an issue, and possibly in need of
settings in configure.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.