freebsd 15 32 bit wine issues

hello. i have been trying to fix the issue i am having with wine so i can run 32 bit programs. i tried using pkg32.sh but all that did was tell me that wine and wine64 were different versions. i tried installing wine-devel, but pkg32.sh still installs wine-devel 10, still causing a version mismatch.
Wiki:
wine [wine-10.13] and wine64 [wine-11.7] versions do not match!

Try updating 32-bit wine with
    /usr/local/share/wine/pkg32.sh upgrade
If you are on FreeBSD 15, you can use the old repository
    /usr/local/share/wine/pkg32.sh --old upgrade -r FreeBSD-ports
running pkg32.sh --old upgrade -r FreeBSD-ports still does not install the correct version of wine. i want to run older windows software, is there any way to fix this at all.
 
I had this issue as well. If I remember I changed sources to latest and updated and ran old upgrade option. 32-bit games are now working on 15 on my systems with wine 11.
 
i want to run older windows software, is there any way to fix this at all.

I am running 3x - 32 bit old Windows games on FreeBSD wine on 15.0 using just pkgs - here's what I have installed:

15.0-RELEASE-p8
Code:
wine-devel-allaudio-11.5,1     Microsoft Windows compatibility environment
wine-gecko-devel-2.47.4_1      Gecko Layout Engine for Wine development branch (HTML support)
wine-mono-devel-11.0.0         Mono .NET implementation for Wine development branch
winetricks-20260125            Easy way to work around problems in Wine
You can swap the allaudio wine for:

wine-devel-11.5,1 Microsoft Windows compatibility environment

NOTE that I have also had success with the Proton (aka Steam) version of wine:

wine-proton-9.0.3 Wine with a bit of extra spice

Good Luck !
 
Looking at freshports, here all the available version:
It appears that for an unknown reason we got no latest build done for i386, and I got no fallout message about it.
Hence no update I guess.

You could build the new wow64 variant available here: https://reviews.freebsd.org/D56178

1779243036719.png
 
It appears that for an unknown reason we got no latest build done for i386, and I got no fallout message about it.
If it got skipped because a dependency failed then you won't get a fallout message. The dependency gets the fallout message, skipped port builds don't.

the last run crashed entirely.
Indeed. Can't tell what the reason for the crashed build is though. But it sometimes happens on my own build server too. Usually because I have something in my build list that disappeared from the ports tree.
 
Back
Top