Wine 1.9.3 and git version doesn't compile from source

Questions about Wine on Linux
Locked
Rinaldus
Level 1
Level 1
Posts: 6
Joined: Sun Jun 29, 2008 8:48 am

Wine 1.9.3 and git version doesn't compile from source

Post by Rinaldus »

I try to compile wine 1.9.3 and then tried to compile the git version, but always get error during compilation. I never got any problems with 1.9.2 and below versions. Tried it on 2 computers with the same results.
configure log: http://pastebin.com/bNfZVfet
make log: http://pastebin.com/g29Zv3YE

I use Gentoo Linux with GCC 5.3.0
Top
User avatar
Bob Wya
Level 12
Level 12
Posts: 3068
Joined: Sat Oct 16, 2010 7:40 pm

Re: Wine 1.9.3 and git version doesn't compile from source

Post by Bob Wya »

Rinaldus wrote:I try to compile wine 1.9.3 and then tried to compile the git version, but always get error during compilation. I never got any problems with 1.9.2 and below versions. Tried it on 2 computers with the same results.
configure log: http://pastebin.com/bNfZVfet
make log: http://pastebin.com/g29Zv3YE

I use Gentoo Linux with GCC 5.3.0
I sadly cannot read Eastern European error messages - but it's probably that there's a bug in GCC 5.2.0(+) and stack alignment. See https://bugs.gentoo.org/show_bug.cgi?id=574044
It's exposed by a recent change in the Wine configuration file include/windef.h - to force enable force_align_arg_pointer (probably to increase performance - I can't remember).

If you're interested in getting a quick fix... the ebuilds for Wine in my overlay bobwya (it's listed in Layman) - workaround this issue automatically.

I've also altered customised the ebuilds so that Wine +staging live builds will build against Wine Staging git commit hashes (and then indirectly against Wine commit hashes). In recent months (since Wine Staging went "official") Wine Staging commit hashes can be automatically linked back to corresponding Upstream Wine commit... In an ideal world (hah, hah) this means that my wine-9999.ebuild should always compile with +staging enabled. Same cannot be said of the in-tree wine-9999.ebuild. The in-tree ebuild references git commits against Wine git. However this introduces 2 problems:
  • Wine Staging git always lags Wine git (= build failures at origin/head)
  • Wine commit hashes can not be easily reversed to get the corresponding Wine Staging commit hash (you can only flag a potential build failure when the trees are out-of-sync at origin/head)
Typically the in tree wine-9999.ebuild will fail when Wine Staging git lags behind the Upstream Wine git (uhm, but it always does = fail)

With my wine-9999.ebuild you can supply any recent(ish) EGIT_COMMIT or (an EGIT_BRANCH) environment variable to build against either a Wine (-staging) or a Wine Staging (+staging) commit hash, e.g.:

Code: Select all

env EGIT_COMMIT="*" emerge =app-emulation/wine-9999
* = standard SHA-1 git commit hash

I've even included a little script, in the app-emulation/wine package, that will do the reverse conversion of a Wine commit to Wine Staging commit (by brute-force reverse processing through the Wine Staging git tree)!

Let me know if you've got any issues with my overlay app-emulation/wine package 8) It's on GitHub here - if you just want a local copy or to report an issue...

Bob
Top
Locked

Return to “Linux”