CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After installing wine from the repo, I cannot use it:
Code:
$ WINEPREFIX="$HOME/prefix32" WINEARCH=win32 wine app.exe
wine: '/home/notooth/prefix32' is a 32-bit installation, it cannot support 64-bit applications.
$ WINEPREFIX="$HOME/prefix64" WINEARCH=win64 wine64 app.exe
wine: Bad EXE format for app.exe.
$ which wine
/usr/bin/wine
$ which wine64
/usr/bin/wine64
My point is that you were changing where to look for wine. /user/bin should be in your PATH. Don’t set WINEPREFIX, just login as the regular user and run
Puppy's way of handling this is for devs, at release of any new, 'official' version, to produce an SFS package which adds all the possible, commonly-required 32-bit dependencies to the /usr/lib32 directory. Following which you merely issue
Quote:
ldconfig
....to integrate it with the system. Because it's an SFS package, and can be loaded/unloaded 'on-the-fly', you just 'install' it as & when required....
Puppies always use the 32-bit versions of WINE, because WINE64 is just a pain in the a**e to get running. At all. Personally, I use a single, external 'install' of WINE in its own dedicated directory, sym-linked, via custom-made .pet packages, into 32- and 64-bit Puppies alike. Once set-up in any Puppy, it just works, OOTB, in any other.
Custom Menu entries permit me to access WINE from whatever Puppy I happen to be using for the day.
Mike.
Last edited by Mike_Walsh; 03-12-2020 at 09:22 AM.
$ alternatives --display wine
wine - status is auto.
link currently points to /usr/bin/wine64
/usr/bin/wine64 - priority 10
slave wine-preloader: /usr/bin/wine64-preloader
Current `best' version is /usr/bin/wine64.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.