wine command can point to 64bit Wine instead of 32bit Wine on some systems - must be handled better

[stefnet00]

Dear all,

I'm trying to use a windows .DLL on a headless CentOS 7.8 server but can not get it running.
The simplest test was to call a simple hello world script on windows side using zugbruecke's wine-python script:

wine-python test.py 

The result is

wine: '~/.zugbruecke/win32-wine' is a 32-bit installation, it cannot support 64-bit applications.

Which is unclear to me. Everything on windows side should be 32-bit.

Can zugbruecke execute wine on headless servers? And if not, how to configure wine on the headless server?

Xvfb is installed but it did not make any difference.

Xvfb :1 -screen 0 1280x960x24 &
DISPLAY=:1 ./wine-python test.py

One thing is remarkable. The directory ~/.zugbruecke/win32-wine/drive_c is empty. On my workstation (openSUSE Leap 15.1) it contains lots of files.

[s-m-e]

is a 32-bit installation, it cannot support 64-bit applications.

This appears to be coming from wine itself. Not sure why though.

Can zugbruecke execute wine on headless servers?

Yes, absolutely.

The directory ~/.zugbruecke/win32-wine/drive_c is empty.

This supports the hypothesis that wine is failing to start (at all).

I have not (yet) looked into how wine is packaged on CentOS / RedHat. On openSUSE, there are usually two packages: wine and wine-32bit. Again on openSUSE, they give you two binaries: wine (which is 32 bit) and wine64 (which is obviously 64 bit). I suspect that the naming and packaging is different on CentOS. Can you please check?

[stefnet00]

Can you please check?

On CentOS its the other way around. wine is 64 bit.

$ whereis wine
wine: /usr/bin/wine /usr/lib64/wine /usr/share/wine /usr/share/man/man1/wine.1.gz
$ l /usr/bin/wine
/usr/bin/wine -> /etc/alternatives/wine
$ l /etc/alternatives/wine
/etc/alternatives/wine -> /usr/bin/wine64

A 32 bit version is not available. I guess thats the problem.

[s-m-e]

It appears to be a common problem and there also appears to be a much desired solution :) Let me know if it works for you. You may have to alter some code in zugbruecke to make it work with binaries with other names though, see here. I'll check if I can provide a clean solution and an update.

[stefnet00]

Great, I changed the names in wine_cmd in the interpreter.py like you said and switched to wine64. That worked!

I'll see if they install wine32 from a third party repository. If not I'll have to get a 64 bit version of the DLL.

[stefnet00]

The 32bit version of wine has been installed and replaced /usr/bin/wine. Hence zugbruecke works like expected.
Don't know what happens if wine64 is installed after wine32.

[s-m-e]

I've made a note - I'll test CentOS more carefully and add the findings to the documentation. Thanks for making me aware of it.

[s-m-e]

Re-opening, because this deserves better error-handling on zugbruecke's side.