http://bugs.winehq.org/show_bug.cgi?id=58286
Bug ID: 58286 Summary: Cannot create a 64-bit wineprefix with old wow64 Product: Wine Version: 10.8 Hardware: x86-64 OS: Linux Status: NEW Keywords: download, regression, source, win64 Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs@winehq.org Reporter: imwellcushtymelike@gmail.com CC: julliard@winehq.org Regression SHA1: cb87d40cd4a8837826ea76efc91371ab09eb9d63 Distribution: Ubuntu
Created attachment 78634 --> http://bugs.winehq.org/attachment.cgi?id=78634 config.logs
Since commit cb87d40cd4a8837826ea76efc91371ab09eb9d63 I have been unable to create a 64-bit wineprefix when I build Wine. This is running without first using "make install".
wine: created the configuration directory '/tmp/wine/wineprefix' wine: WINEARCH set to win64 but '/tmp/wine/wineprefix' is a 32-bit installation.
Whereas /tmp/wine/wineprefix does not initially exist. It is created by Wine, but then insists it's 32-bit and immediately exits.
- New wow64 works fine - 32-bit works fine - -O0 and -O2 make no difference - The prebuilt debs work fine
commit cb87d40cd4a8837826ea76efc91371ab09eb9d63 Author: Alexandre Julliard julliard@winehq.org Date: Fri Feb 14 15:32:19 2025 +0100
makefiles: Create wine as a symlink to tools/wine/wine.
This commit cannot be reverted, but checking out the commit before fixes the issue.
My process as per https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine#shared-wow64
1. Build 64-bit-only 2. Build 32-bit 3. Build 64-bit-wow
This is the same process I have always used.
I know there's been a number of changes in this area so I don't know how to work around it.
In all cases I use Debian Stable chroots (with schroot) but the same result using Debian Testing.
If it's me doing something stupid then I apologise in advance.
http://bugs.winehq.org/show_bug.cgi?id=58286
--- Comment #1 from Ken Sharp imwellcushtymelike@gmail.com --- Created attachment 78635 --> http://bugs.winehq.org/attachment.cgi?id=78635 Console
I missed an important point:
wineboot = OK WINEARCH=win32 wineboot = OK WINEARCH=win64 wineboot = fail WINEARCH=wow64 wineboot = fail
So it's when WINEARCH is forcing a new 64-bit wineprefix.
http://bugs.winehq.org/show_bug.cgi?id=58286
--- Comment #2 from Ken Sharp imwellcushtymelike@gmail.com --- Also, I tried with-mingw and without-mingw and it makes no difference.
http://bugs.winehq.org/show_bug.cgi?id=58286
--- Comment #3 from Alexandre Julliard julliard@winehq.org --- It's hard to tell without seeing the details of your chroot, but it sounds like the 32-bit build doesn't see the 64-bit one. Are you running from the wow64 build dir? You should have a loader-wow64 symlink in there.
http://bugs.winehq.org/show_bug.cgi?id=58286
--- Comment #4 from Ken Sharp imwellcushtymelike@gmail.com --- Created attachment 78637 --> http://bugs.winehq.org/attachment.cgi?id=78637 Directory tree
I've attached some text from my mad ramblings at https://forum.winehq.org/viewtopic.php?p=147464#p147464 and the view of the tree from within the chroots used. I don't know if any of it is of any use.
The builds take place in the chroots and they can see each other. They don't run in the chroots though, I run them directly (Ubuntu). It's always worked well.
http://bugs.winehq.org/show_bug.cgi?id=58286
--- Comment #5 from Ken Sharp imwellcushtymelike@gmail.com ---
Are you running from the wow64 build dir?
Sorry, I didn't answer that.
I am running wine64/wine (the wow64 build).
http://bugs.winehq.org/show_bug.cgi?id=58286
--- Comment #6 from Alexandre Julliard julliard@winehq.org --- I see, that's because the wine symlink points into the 32-bit only dir. You probably need to build that one as wow64 too, or else run wine from the wine64only dir.
http://bugs.winehq.org/show_bug.cgi?id=58286
--- Comment #7 from Ken Sharp imwellcushtymelike@gmail.com --- Running from wine64only does indeed work! Tested with 32-bit and 64-bit programs and everything is back to normal.
Does that make this an invalid bug? The behaviour has changed, apparently. Assuming I was compiling correctly in the first place (I did use the [old] Wiki as a guide).
The documentation (Wiki) does need updating. I'll look at that later if someone doesn't beat me to it. (Please beat me to it)
http://bugs.winehq.org/show_bug.cgi?id=58286
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #8 from Alexandre Julliard julliard@winehq.org --- I've added e6677fe356686186ac7b75552f2263f035360d47 which makes it possible to use --enable-tools in the wow64 tree instead of using a separate 32-bit tools tree.
Resolving FIXED, though it could as well be marked INVALID, it's more a documentation issue than a real bug.