Solved confusion about wine64

[ko56]

Hi, I am on FreeBSD 14.3-RELEASE, and I've installed the wine-devel pkg, version 10.10.
I am confused about what the following is saying:

ko@hn ~]$ wine64 /usr/local/lib/wine/x86_64-windows/wineconsole.exe

/home/ko/.i386-wine-pkg//usr/local/bin/wine doesn't exist!

Try installing 32-bit Wine with
    /usr/local/share/wine/pkg32.sh install wine-devel mesa-dri

If using Poudriere, please make sure your repo is setup to use FreeBSD:14:i386

and create symlinks for

  FreeBSD:14:amd64 and
  FreeBSD:14:i386

to the relevant output directories. See pkg.conf(5) for more info.
[ko@hn ~]$

I believe that above I am trying to run a 64-bit Windows application, so wine64 should do it.
And I shouldn't need 32-bit wine. Apparently not so?

Further confusion:

[ko@hn ~]$ file /usr/local/lib/wine/x86_64-windows/wineconsole.exe
/usr/local/lib/wine/x86_64-windows/wineconsole.exe: PE32+ executable for WINE (GUI), x86-64, 13 sections
[ko@hn ~]$

A web search seems to indicate that PE32+ is "Windows 64-bit format".
Thanks for any help.

 

[drr]

I remember having to make a sym link to sort out a similar issue when I used wine briefly long ago; I do not use it at the moment and can't remember the specifics.

 

[ko56]

The main thing is that pkg wine and pkg wine-devel behave very differently.

wine, even without ~/.i386-wine-pkg works fine:
1) E.g. wine64 winecfg works, but not wine winecfg.
2) ~/.wine is created.

However, wine-devel doesn't do either 1) or 2)!
Its behavior doesn't change even if you first do 2) with wine and then
uninstall wine and install wine-devel.

Now why they behave so differently is an open question.

 

[sko]

I believe that above I am trying to run a 64-bit Windows application, so wine64 should do it.
And I shouldn't need 32-bit wine. Apparently not so?

Windows land is still a dumpster fire of mixed 64- and 32-bit binaries and libraries, so for an alleged 64bit application you will often also need to be able to deal with 32bit cruft.
E.g. a classical scenario: the installer is a 32bit binary while the installed program is 64bit. In case of games their launchers are often also 32bit but the game they load is 64bit... as said: it's a dumpster fire.

 

[ko56]

Windows land is still a dumpster fire of mixed 64- and 32-bit binaries and libraries, so for an alleged 64bit application you will often also need to be able to deal with 32bit cruft.
E.g. a classical scenario: the installer is a 32bit binary while the installed program is 64bit. In case of games their launchers are often also 32bit but the game they load is 64bit... as said: it's a dumpster fire.

Yes, I've come across the problem of the 32-bit installer for a 64 bit application. Painful!