pkg -o ABI_FILE=/usr/lib32/libc.so.7 -o INSTALL_AS_USER=true -o RUN_SCRIPTS=false --rootdir /home/nomad/.i386-wine-pkg install wine mesa-dri pkg: Unable to determine the ABI, none of the ABI_FILEs can be read. pkg: Cannot parse configuration file!
Installed NomadBSD 14.1 , ok, success. Then installed Wine following the chapter 13 page of FreeBSD , ok, success.
Try to run a Windows program.exe with Wine, the alert of wine configuration-in-progress appears for some seconds, then gives me the above mentioned results after the attempt to run the windows exetutable.
Wine is perfectly working in 14.0 release which I kept, since I knew the fightings I was going to face for this to work. Infact also having it working in 14.0 requested a serious effort.
Can anyone suggest a solution for this issue?
Thank you much
can say I’ve solved the matter with the help received on FreeBSD forum. It should be same done for this issue years ago, really not easy to remember because the understanding of what to do comes step by step by testing different ways upon message responses on the terminal. Wine installation on FreeBSD is not crystal-clear as it should be, mainly depending from the fact that 32 bit libraries are not included in the recent FreeBSD releases projected almost exclusively for 64 bit architecture, while a Windows 32 bit application needs those libraries.
However, the short story is: the 32-bit libraries to add in NomadBSD 14.1 are in the lib32.txz file downloadable from http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/14.1-RELEASE .
Once extracted-copied the files in the right paths as for folder three showing in the deployed archive, I repeated the installation of Wine. Then trying to run program.exe first time, it asked for /usr/local/share/wine/pkg32.sh install wine mesa-dri , so gave such command and it completed the necessary pkg operations. But after that it may still not run any of the Windows executable, if many lines warning of “files-dlls missing” prevent the program execution. Finally have read the fix on another sitepage for this other kind of issue: when you’re warned about lot of dlls missing, just uninstall wine package, delete the .wine directory, reinstall wine package .
Now the Windows executable are up 'n running