Summary: | app-emulation/wine compilation hang for versions >=1.9.22 with gcc-5.4.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrés Becerra Sandoval <andres.becerra> |
Component: | Current packages | Assignee: | Wine Maintainers <wine> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bob.mt.wya, egorov_egor, herrtimson, isak50, mail, vityokster |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78911 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrés Becerra Sandoval
2017-03-18 16:53:56 UTC
Viktor Yu. Kovalskiy submitted a bug report upstream (URL). Can you paste the output of: grep PATCH_VER /var/db/pkg/sys-devel/gcc-5.4.0-r3/gcc-5.4.0-r3.ebuild Also, I successfully compiled wine-2.0 with gcc-5.4.0-r3 about a day ago on a ~amd64 system, so it might be worth investigating whether anyone can reproduce this on a stable system. I test compilation of >=app-emalution/wine-1.9.22 and found that compilation fine with CFLAGS="-O2 -march=i686 -mtune=generic" but hangs with CFLAGS="-O2 -march=i686". (In reply to NP-Hardass from comment #2) > Can you paste the output of: > grep PATCH_VER /var/db/pkg/sys-devel/gcc-5.4.0-r3/gcc-5.4.0-r3.ebuild > > Also, I successfully compiled wine-2.0 with gcc-5.4.0-r3 about a day ago on > a ~amd64 system, so it might be worth investigating whether anyone can > reproduce this on a stable system. grep PATCH_VER /var/db/pkg/sys-devel/gcc-5.4.0-r3/gcc-5.4.0-r3.ebuild PATCH_VER="1.3" (In reply to NP-Hardass from comment #2) > Can you paste the output of: > grep PATCH_VER /var/db/pkg/sys-devel/gcc-5.4.0-r3/gcc-5.4.0-r3.ebuild > > Also, I successfully compiled wine-2.0 with gcc-5.4.0-r3 about a day ago on > a ~amd64 system, so it might be worth investigating whether anyone can > reproduce this on a stable system. Sorry, meant to say on a amd64 system, not an ~amd64 system. What about changing the -O level? Does -O1 allow it to compile? I'll see if I can get a system up and running soon to test more extensively locally. Alright, I successfully reproduced the issue on a stable system with gcc-5.4.0{,-r3} wine env: USE="-abi_x86_64" CFLAGS="-O2 -march=i686" I'll see if I can get a test of 5.4.0 on another distro so we can see if it appears Gentoo specific (before I go digging further on our end) *** Bug 632038 has been marked as a duplicate of this bug. *** Upstream (GCC) bug was reported: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78911 I think we should report information from our Bugzilla to GCC Bugzilla. This has long been fixed upstream (GCC in this case). Please close this bug report. |