Summary: | app-emulation/wine-1.9.4 fails to build - dlls/advapi32/crypt_md4.c:134:1: internal compiler error: in choose_baseaddr, at config/i386/i386.c:10412 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anton Gubarkov <anton.gubarkov> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bkohler, fcoiffie, rzubaly, ua_gentoo_bugzilla, zeekec |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | collection of build logs |
Description
Anton Gubarkov
2016-03-07 06:27:26 UTC
Created attachment 427656 [details]
collection of build logs
wine should not be built with O2. They even say it on their HP https://wiki.winehq.org/Building_Wine#Compiler_Optimizations_.26_Call-Stacks Therefore, activate custom-cflags for wine in /etc/portage/package.use app-emulation/wine custom-cflags Then add /etc/portage/package.env app-emulation/wine debug-cflags and in /etc/portage/env/debug-cflags CFLAGS="-O0 -pipe -g2 -ggdb -frecord-gcc-switches" CXXFLAGS="${CFLAGS}" FEATURES="${FEATURES} nostrip" tl;dr CFLAGS="" emerge wine should work (In reply to Steffen from comment #2) > wine should not be built with O2. They even say it on their HP > https://wiki.winehq.org/Building_Wine#Compiler_Optimizations_.26_Call-Stacks > > Therefore, activate custom-cflags for wine in /etc/portage/package.use > app-emulation/wine custom-cflags > > Then add /etc/portage/package.env > app-emulation/wine debug-cflags > > and in /etc/portage/env/debug-cflags > CFLAGS="-O0 -pipe -g2 -ggdb -frecord-gcc-switches" > CXXFLAGS="${CFLAGS}" > FEATURES="${FEATURES} nostrip" > > tl;dr > CFLAGS="" emerge wine > should work Thanks, that fixes it. The recommended "-O1 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline" works too here (just omitted -g for my production environment). I think this should be implemented in the ebuild though, not through custom-cflags and particularly not on a per-user basis. *** This bug has been marked as a duplicate of bug 574044 *** |