[Bug 57611] New: ./configure --enable-archs=i386 builds, but doesn't run

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57611

Bug ID: 57611
           Summary: ./configure --enable-archs=i386 builds, but doesn't
                    run
           Product: Wine
           Version: 9.19
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Keywords: download
          Severity: normal
          Priority: P2
         Component: ntdll
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: Debian

I tried building a 32-bit only Wine with the new style build:

$ ./configure --disable-tests --enable-archs=i386 && make -j$(nproc)

That builds fine. Running anything, however, fails:

$ ./wine cmd
wine: created the configuration directory '/home/austin/.wine'
wine: failed to open L"C:\windows\system32\wineboot.exe": c0000135
0024:err:environ:run_wineboot failed to start wineboot c0000135
wine: failed to load start.exe: c0000135

There are some legacy applications that don't work in a 64-bit prefix (e.g., in
winetricks dotnet11/jet40/mdac27/mdac28/psdk2003/wmp10).

[Bug 57611] ./configure --enable-archs=i386 builds, but doesn't run

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57611

Fabian Maurer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 57611] ./configure --enable-archs=i386 builds, but doesn't run

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57611

--- Comment #1 from Alexandre Julliard  ---
A 32-bit only build cannot possibly work in new wow64 mode, the whole point of
new wow64 is that it thunks to 64-bit.

[Bug 57611] ./configure --enable-archs=i386 builds, but doesn't run

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57611

--- Comment #2 from Austin English  ---
(In reply to Alexandre Julliard from comment #1)
> A 32-bit only build cannot possibly work in new wow64 mode, the whole point
> of new wow64 is that it thunks to 64-bit.

Makes sense; in that case, seems like configure shouldn't allow this
configuration to be built.

Long term, are we considering 32-bit prefixes to be deprecated or is there some
other plan?

[Bug 57611] ./configure --enable-archs=i386 builds, but doesn't run

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57611

--- Comment #3 from Alexandre Julliard  ---
(In reply to Austin English from comment #2)
> (In reply to Alexandre Julliard from comment #1)
> > A 32-bit only build cannot possibly work in new wow64 mode, the whole point
> > of new wow64 is that it thunks to 64-bit.
>
> Makes sense; in that case, seems like configure shouldn't allow this
> configuration to be built.

Possibly; currently we allow any combination of platforms to be built, even if
the resulting build is not useful in isolation.

Note that the libraries built that way are perfectly usable if combined with a
separate 64-bit build. It may be useful for instance if you want to test a
patch without having to rebuild the 64-bit side, or if you want a single i386
build to use on both x86-64 and arm64.
> Long term, are we considering 32-bit prefixes to be deprecated or is there
> some other plan?

Yes, they are deprecated, they no longer exist on Windows either. Any app that
cannot be made to work in a 64-bit prefix should be treated as a bug.