[Bug 51051] Build fails when LTO is enabled

WineHQ Bugzilla wine-bugs at winehq.org
Sun May 9 07:47:54 CDT 2021


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

--- Comment #13 from Sveinar Søpler <cybermax at dexter.no> ---
@Zebediah Figura
I haven't spent too much fiddling with this, but i have tried to build with
-flto both with gcc-10.3 and clang-10 to no avail. So afaik atm i cannot
conclude that wine is able to be built with -flto.. atleast not on ubuntu.

@Rosanne DiMesio
Did you try to do a standalone build on hirsute? outside of debbuild i mean?

Cos i just did a regular wine-staging (6.8) build with:
configure --enable-win64
make -j4

It built without issues. Same for the 32-bit build

I basically followed the https://wiki.winehq.org/Building_Biarch_Wine_On_Ubuntu
recipe, except i built 32-bit with
"PKG_CONFIG_PATH="/usr/lib/i386-linux-gnu/pkgconfig" instead of using LCX. (The
only package that needs "switching" is libgcrypt20-dev that is no mulilib
installable).

If the debbuild "default" is the only thing that causes -flto to be used, do
wine's configure even need to consider that? I mean since it is debbuild that
is actually running configure with the -flto flag, and it does not happen if
you run "plain" configure. I am fairly sure if i post a builderror due to me
setting some optimization flags would come back to "Have you tried to compile
by just running configure?". (Cos -march=native, -O3++ is various optimization
flags not always working stellar on wine for various reasons)

Thoughts?

-- 
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.


More information about the wine-bugs mailing list