wine-10.0-rc3: building wine from source: running locally within build tree, can not load any *.exe

Questions about Wine on Linux
Locked
dedrekt
Newbie
Newbie
Posts: 1
Joined: Thu Jan 02, 2025 5:52 pm

wine-10.0-rc3: building wine from source: running locally within build tree, can not load any *.exe

Post by dedrekt »

Firstly, wine installation packaged under pacman (wine-staging) did not seem to run windows executables, and subsequently I encountered a 64-bit installer which required 64-bit wine binaries. Removing wine /w pacman and obtaining the source tarball (namely, wine-10.0-rc3.tar.xz) and configuring with:

Code: Select all

${builddir}configure  --enable-win64 --disable-tests --enable-archs=x86_64 --prefix=$prefix --with-x  --x-includes=/usr/include/X11
( very much possible of a misconfiguration or missing flags to add to for options I have enabled )

Here's the config.log if that's relevant.

, and running the loader binary (the installation prefix is contained in the build dir itself, prefix=`pwd`/usr/loca/wine), I'm getting a ntdll (0xc0000135) related error as I assume the case of not launching exe(s) to be.

Code: Select all

$ WINESERVER=usr/local/wine/bin/wineserver WINEPREFIX=`pwd`/.wine64 $winebin /tmp/eq-apo.exe

0128:err:environ:init_peb starting L"Z:\\tmp\\eq-apo.exe" in experimental wow64 mode
wine: failed to load L"\\??\\C:\\windows\\syswow64\\ntdll.dll" error c0000135
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: 0024:err:start:fatal_error FormatMessage failed
00ec:fixme:wineusb:add_usb_device Interface 1 has 7 alternate settings; using the first one.
00ec:fixme:wineusb:add_usb_device Interface 1 has 7 alternate settings; using the first one.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
00cc:fixme:wineusb:query_id Unhandled ID query type 0x5.
The eventual fatal error is " FormatMessage failed". I'm not sure if this is causaly linked to the previous error concerning ntdll.dll. "c0000135" seems to be a "file not found" type of error if my information is sane.

Looking at syswow64 in the freshly created wineprefix, it was empty. So naively, I copied the syswow64/*.dll in the original wineprefix created by pacman-installed wine-staging in $HOME to that place, but seems to reflect no changes at all.

I'm very much new to wine, and I barely know how wine internally works or even the interface it exposes to the end-users. So I'm pretty clueless speaking here.

If I get a vanilla build of wine to work, I have plans to apply some patches and tweak some configs, so I would very much like to stick with this building-from-source approach in running wine.

{
Note1: exe provided automatically by wine in $WINEPREFIX work
Note2: I have gone through [url=https://gitlab.winehq.org/wine/wine/-/w ... lding-Wine
https://gitlab.winehq.org/wine/wine/-/w ... lding-Wine[/url]
Note3: Running packaged installation as in wine-staging causes dump of call stacks and memory related crashes when launching programs
}
Locked