I wanted to install an old Win32 game, and noticed an issue which I haven't had on 14.0, 13.2/3.
So, I execute "wine UTDemo348.exe" and get the expected error since I've not yet installed anything 32bit:
That I must run: /usr/local/share/wine/pkg32.sh install wine mesa-dri
However, doing so I get the following output:
I eventually got it to work by reading what was inside the shell script, and just changing it up a bit. This is what worked:
This is probably something which can be very easily fixed. I apologize if this isn't the place to reach out about such an issue, but I don't have much of a bug-report resume, so wanted to rule out possible error on my side. As I said, I got this working fine but I know it can be discouraging when things don't work as expected especially for new users.
So, I execute "wine UTDemo348.exe" and get the expected error since I've not yet installed anything 32bit:
That I must run: /usr/local/share/wine/pkg32.sh install wine mesa-dri
However, doing so I get the following output:
Code:
pkg -o ABI=FreeBSD:14:i386 -o INSTALL_AS_USER=true -o RUN_SCRIPTS=false --rootdir /home/ben/.i386-wine-pkg install wine mesa-dri
Updating FreeBSD repository catalogue...
pkg: Repository FreeBSD has a wrong packagesite, need to re-create database
Fetching meta.conf: 100% 178 B 0.2kB/s 00:01
Fetching data.pkg: 100% 7 MiB 2.3MB/s 00:03
Processing entries: 0%
pkg: Newer FreeBSD version for package zzuf:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1400097
- running kernel: 0
pkg: repository FreeBSD contains packages for wrong OS version: FreeBSD:14:i386
Processing entries: 0%
Unable to update repository FreeBSD
Error updating repositories!
I eventually got it to work by reading what was inside the shell script, and just changing it up a bit. This is what worked:
Code:
pkg -o INSTALL_AS_USER=true -o RUN_SCRIPTS=false --rootdir "/home/ben//.i386-wine-pkg" "$@" install wine mesa-dri
This is probably something which can be very easily fixed. I apologize if this isn't the place to reach out about such an issue, but I don't have much of a bug-report resume, so wanted to rule out possible error on my side. As I said, I got this working fine but I know it can be discouraging when things don't work as expected especially for new users.