wine-1.1.30 fails to emerge, I have attached the compile log. If I add threads to IUSE in the ebuild, and enable the threads use flag it compiles fine. Maybe this is an upstream bug? Reproducible: Always
Created attachment 205327 [details] emerge --info
Created attachment 205328 [details] build log
Created attachment 205329 [details] Patch that fixes it
Created attachment 205342 [details] OpenAL_build.log Wine also fails to build with openal.
Same symptoms as original reporter. Same solution (add threads to IUSE in ebuild) makes wine compile.
It appears the problem is that wine simply does not build when configured using --without-pthread. Since the useflag was omitted in IUSE, the use of $(use_with threads pthread) unconditionally emits this configure option. Adding threads to IUSE allows one to enable the flag and thus build wine successfully, but the failure persists if the useflag is disabled.
not sure where that got to, but should be fixed now http://sources.gentoo.org/app-emulation/wine/wine-1.1.30.ebuild?r1=1.1&r2=1.2 http://sources.gentoo.org/app-emulation/wine/wine-9999.ebuild?r1=1.43&r2=1.44
Just a heads up, I tested a vanilla wine-1.1.30 configured with --without-pthread and it fails the same way. I have reported the bug upstream: http://bugs.winehq.org/show_bug.cgi?id=20196. So I think we should keep an eye on this, or perhaps remove the threads IUSE and always add --with-pthread? BTW. Thanks a lot for always keeping wine up to date!
The wine devs do not want to fix the build or remove the configure option, so I don't think the ebuild should expose that USE flag at all. What are your thoughts?
*** Bug 328649 has been marked as a duplicate of this bug. ***
Thanks for the Cc vapier. Why is this marked as fixed if the build still fails?
I filed bug 328649 because this bug didn't appear in searches for "wine threads" open bugs. Since this issue is *not* fixed, can we please either re-open or close as "wontfix"? Or, as a better fix, hard-enable threads and leave this bug as resolved.
*** Bug 348685 has been marked as a duplicate of this bug. ***
Flag threads not only for wine, some people turn off it globally and receive a compilation error for wine and ask questions at forums. And as has marked Christohper Harrington, this bug in search isn't displayed. Whether is better to remove a flag threads from ebuild at all? Thanks.
Since building wine with USE=-threads on a glibc-based system is guaranteed to fail, all wine ebuilds have now been updated with REQUIRED_USE="elibc_glibc? ( threads )". Hopefully that will prevent anyone else from running into this issue in the future.
