How to Install Wine 32-bit on CentOS 7
Posted on In Linux, Software, TutorialSince version 7, RHEL has only x86-64 versions. The same thing happens to CentOS 7. In CentOS 7/EPEL, there is only package for Wine x86-64. However, many Windows .exe files are 32-bit. Even there are 64-bit versions for some software, their installation file is 32-bit. And for some certain software such as Office 2007, 32-bit wine is preferred.
In this post, we will check how to install 32-bit Wine on CentOS 7. If you would like to install 32-bit Wine on CentOS 8, please check How to Install Wine 32-bit on CentOS 8.
- It is confirmed that this method works for Wine 4.10.0 by lukesoft.
- It is confirmed that this method works for Scientific Linux 7.2 too by Steve.
- It is confirmed that this method works for Wine 2.0 too by Victor Schulz and gretzware.
- It is confirmed that this method works for 2.17 development too by gretzware. Note it needs libXfixes-devel .
Table of Contents
One single script to build and install Wine
The whole process in this post has already been written as a shell script.
- If you would install wine 1.8.7 to 4.10.0, please use install-wine-i686-centos7.sh.
- If you would install wine 5, please use install-wine-5.0-centos7.sh.
You may download the script and run it directly as root to install wine of version <version> such as 1.8.7, 2.0.2.
# ./install-wine-i686-centos7.sh [<version>]or
# ./install-wine-5.0-centos7.sh [<version>]Build and install Wine manually step by step
The following part of this post introduces what each step does.
Erase old wine versions installed
If you ever installed wine packages, erase them first as we will build wine from the source.
yum erase wine wine-*Install packages needed to build wine
We are going to install the packages needed to build wine. These may not be sufficient depending on your base installation packages. If later steps complain that some packages are missing, you can install them.
yum install samba-winbind-clients -y
yum groupinstall 'Development Tools' -y
yum install libjpeg-turbo-devel libtiff-devel freetype-devel -y
yum install glibc-devel.{i686,x86_64} libgcc.{i686,x86_64} libX11-devel.{i686,x86_64} freetype-devel.{i686,x86_64} gnutls-devel.{i686,x86_64} libxml2-devel.{i686,x86_64} libjpeg-turbo-devel.{i686,x86_64} libpng-devel.{i686,x86_64} libXrender-devel.{i686,x86_64} alsa-lib-devel.{i686,x86_64} -y
# ... and more ...
# Check the `install-wine-i686-centos7.sh` script for more packages needed.
Download and unpack the source package
Here, we use a variable $ver to specify the version we want to install. It will be used in later steps too.
ver=2.0.2 # We will use this as the example.
vermajor=$(echo ${ver} | cut -d'.' -f1)
verurlstr=$(echo ${ver} | cut -d'.' -f1,2)
cd /usr/src
if "${vermajor}" == "1" ; then
wget http://dl.winehq.org/wine/source/${verurlstr}/wine-${ver}.tar.bz2 -O wine-${ver}.tar.bz2
tar xjf wine-${ver}.tar.bz2
elif "${vermajor}" == "2" ; then
wget http://dl.winehq.org/wine/source/${verurlstr}/wine-${ver}.tar.xz -O wine-${ver}.tar.xz
tar xf wine-${ver}.tar.xz
fiBuild wine 32-bit and 64-bit versions
Make directories for building wine 32-bit and 64-bit versions.
cd wine-${ver}/
mkdir -p wine32 wine64Build the 64-bit version first as 32-bit version building depends on it.
cd wine64
../configure --enable-win64
make -j 4Build the 32-bit version now.
cd ../wine32
PKG_CONFIG_PATH=/usr/lib/pkgconfig ../configure --with-wine64=../wine64
make -j 4Install wine 32-bit and 64-bit versions
Now, we can install Wine. The trick is to install 32-bit version first and then the 64-bit version.
As we are still in the win32 directory, run
make installInstall the 64-bit version:
cd ../wine64
make installBy now, if everything goes well, you have successfully installed the Wine 32-bit and 64-bit versions. You may double-check it with the file command:
$ file `which wine`
/usr/local/bin/wine: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=a83b9f0916e6c0d5427e2c38a172c93bd8023d98, not stripped
$ file `which wine64`
/usr/local/bin/wine64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=4d8e8468402bc63bd2a72c59c57fcad332235d41, not strippedNote the “ELF 32-bit” and “ELF 64-bit” in the file type strings.
Now you can run your 32-bit Windows application on CentOS 7. Enjoy :-)
i just try the script and got this error:
../../../dlls/vbscript/parser.y: conflicts: 7 shift/reduce../../../dlls/winex11.drv/x11drv_main.c: In function ‘process_attach’:
../../../dlls/winex11.drv/x11drv_main.c:536:33: error: ‘SONAME_LIBX11’ undeclared (first use in this function)
void *libx11 = wine_dlopen( SONAME_LIBX11, RTLD_NOW|RTLD_GLOBAL, error, sizeof(error) );
^
../../../dlls/winex11.drv/x11drv_main.c:536:33: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [x11drv_main.o] Error 1
make: *** [dlls/winex11.drv] Error 2
make: *** Waiting for unfinished jobs....
[root@svr1 ~]# wine
-bash: /usr/bin/wine: No such file or directory
what was i am missing?
`SONAME_LIBX11` seems a macro defined by `wine` src. Might be something wrong during the `./configure` step.
Did you use the script or do the steps manually? If you run the script, you might paste the log (the log file is shown at the very beginning of the STDOUT) to let us take a look.
Hi Eric, sorry late to respond. i just figure it out.
And everything is work like a charm.
The updated script can add gstreamer back to work too with other components. Enjoy!
This worked perfectly for me on Scientific Linux 7.2 except that I needed to install glibc-devel.i686 along with the other development packages. Maybe that reflects a difference between Centos 7 and SL 7. No problems after that.
Thanks very much!
Great to know that and thanks for the note! CentOS 7 I used seems already have the ‘glibc-devel.i686’ package before I did this. Added into the installation package list.
Eric Zhiqiang Ma, MANY thanks you man,
So much thanks we done it. I have tried to make it more than few months from time to time and got the same result or just 64bit installed or couple of problems during 32bit building.
Now the everything and you are the greatest man ever for me.
Thanks for save much of my private time.
The everything best to you.
Sign,
Fen
Glad to know it helped!
Hi,
make install on 32 bits is ok but when i try the same on 64 bits src, i got the following error :
gcc -m64 -c -o x11drv_main.o ../../../dlls/winex11.drv/x11drv_main.c -I. -I../../../dlls/winex11.drv \
-I../../include -I../../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe \
-fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers \
-Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith \
-Wlogical-op -gdwarf-2 -gstrict-dwarf -g -O2
../../../dlls/winex11.drv/x11drv_main.c: In function ‘process_attach’:
../../../dlls/winex11.drv/x11drv_main.c:536:33: erreur: ‘SONAME_LIBX11’ undeclared (first use in this function)
void *libx11 = wine_dlopen( SONAME_LIBX11, RTLD_NOW|RTLD_GLOBAL, error, sizeof(error) );
^
../../../dlls/winex11.drv/x11drv_main.c:536:33: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [x11drv_main.o] Erreur 1
make[1] : on quitte le répertoire « /usr/src/wine-1.8.5/wine64/dlls/winex11.drv »
make: *** [dlls/winex11.drv] Erreur 2
any idea ?
PS : excuse my english, I ‘m from Paris
Seems the same error as http://www.systutorials.com/239913/install-32-bit-wine-1-8-centos-7/#comment-131257 . Please check and give some more details as in http://www.systutorials.com/239913/install-32-bit-wine-1-8-centos-7/#comment-131298 so that we can take a look.
I had that same “SONAME_LIBX11 undeclared (first use in this function)” error and found that the problem was I didn’t have the (64bit) libX11-devel.x86_64 installed.
The i686 version is explicitly installed by the yum command in the script but unless your system has this installed previously none of the yum’s in the script will pull it in.
So, do “yum install libX11-devel.x86_64” and re-run and that particular problem should go away.
(the same is true from the xrender, xml, gnutls and png libs too… the 32-bit versions are explicitly yum’ed by the script but your system may not have the 64-bit versions installed)
Good catch! Updated the post and script, making these package handled automatically.
I had to add the alsa-lib-devel packages (both 32 and 64 bits) before compiling, otherwise wine was compiled without sound support.
I was also able to compile the 2.0 version of wine with the script, by changing the version variable and the path in the wget line.
Hi Victor, thanks for the tips. I will add alsa-lib-devel as the default packages required.
And it is great to know it works for 2.0 version too!
Thanks a lot. It worked like a charm
Your instructions are really good, simple and to the point
I just wanted to add for better build support with 99% of the development libraries the following RPMs help in order to install some of these you need epel and nux desktop installed as a repo
make sure to have epel and nux desktop installed before installing these packages
extra 64bit-packages
——————–
yum install glibc-devel libstdc++-devel icoutils openal-soft-devel prelink gstreamer-plugins-base-devel gstreamer-devel ImageMagick-devel fontpackages-devel libv4l-devel gsm-devel giflib-devel libXxf86dga-devel mesa-libOSMesa-devel isdn4k-utils-devel libgphoto2-devel fontforge libusb-devel lcms2-devel audiofile-devel
yum install openldap-devel libxslt-devel libXcursor-devel libXi-devel libXxf86vm-devel libXrandr-devel libXinerama-devel libXcomposite-devel mesa-libGLU-devel ocl-icd opencl-headers libpcap-devel dbus-devel ncurses-devel libsane-hpaio pulseaudio-libs-devel cups-devel libmpg123-devel fontconfig-devel sane-backends-devel.x86_64
extra 32bit-packages
————–
yum install glibc-devel.i686 dbus-devel.i686 freetype-devel.i686 pulseaudio-libs-devel.i686 libX11-devel.i686 mesa-libGLU-devel.i686 libICE-devel.i686 libXext-devel.i686 libXcursor-devel.i686 libXi-devel.i686 libXxf86vm-devel.i686 libXrender-devel.i686 libXinerama-devel.i686 libXcomposite-devel.i686 libXrandr-devel.i686 mesa-libGL-devel.i686 mesa-libOSMesa-devel.i686 libxml2-devel.i686 libxslt-devel.i686 zlib-devel.i686 gnutls-devel.i686 ncurses-devel.i686 sane-backends-devel.i686 libv4l-devel.i686 libgphoto2-devel.i686 libexif-devel.i686 lcms2-devel.i686 gettext-devel.i686 isdn4k-utils-devel.i686 cups-devel.i686 fontconfig-devel.i686 gsm-devel.i686 libjpeg-turbo-devel.i686 pkgconfig.i686 libtiff-devel.i686 unixODBC.i686 openldap-devel.i686 alsa-lib-devel.i686 audiofile-devel.i686 freeglut-devel.i686 giflib-devel.i686 gstreamer-devel.i686 gstreamer-plugins-base-devel.i686 libXmu-devel.i686 libXxf86dga-devel.i686 libieee1284-devel.i686 libpng-devel.i686 librsvg2-devel.i686 libstdc++-devel.i686 libusb-devel.i686 unixODBC-devel.i686 qt-devel.i686 libpcap-devel.i686
Nice list. Thanks for your sharing!
Thanks for this, Eric. And thanks also to the folks who added useful things to this to this in comments. The instructions here allowed me to build Wine64 and Wine32 from scratch using the latest 2.0.1 source from WineHQ. On my wife’s new Centos 7 machine. The one I have built for her in order to wean her away from Windows. I had to get Wine going for a few apps she won’t give up / are used by customers of ours. It took me a couple of goes to get to grips with it. I was missing audio support at first, added in on the third stab at it. But it was an educational experience, and this roadmap made it understandable and easy to do.
Glad to know this post helped!
Hi Eric, thanks so much for this article, it worked flawlessly (with latest wine 2.11), but now I’m a bit confused about the state of my system now, and the best way to run my 32bit Windows app.
I realize that I need to create a 32bit wine prefix, but when launching the app, should I use wine64 (and assume it now knows where to find the 32bit libraries), or should I be using the 32bit /usr/local/bin/wine that was also installed?
Thanks!
Nevermind…just tried to start the app with wine64, and got an informative error message…should have tried that before posting…
Hi Eric,
Your post is simply perfect. Described perfectly and 100% working on CentOS7.
It was not trivial to find an install description for CentOS and you came to help up.
Thanks man.
Good to know it help!
[Help] When configure wine32.. There is gphoto and gstreamer warning in addition only OpenCL, libhal, and OSS when configure wine64. I have double check that required i686 devel of both packages are installed. CentOS 7 1611 and Wine 1.8.7.
configure: OpenCL 32-bit development files not found, OpenCL won’t be supported.
configure: libhal 32-bit development files not found, no legacy dynamic device support.
configure: libgphoto2 32-bit development files not found, digital cameras won’t be supported.
configure: gstreamer-0.10 base plugins 32-bit development files not found, gstreamer support disabled
configure: OSS sound system found but too old (OSSv4 needed), OSS won’t be supported.
Thanks
You may check the comment from David and see wheather these additional packages help: https://www.systutorials.com/239913/install-32-bit-wine-1-8-centos-7/#comment-156429 .
Still, When configure 32 bit:
configure: gstreamer-0.10 base plugins 32-bit development files not found, gstreamer support disabled
IWinehq says:
“PKG_CONFIG_PATH should point to the location of the 32 bit pkgconfig files, probably /usr/lib or /usr/lib32. Without it, the configure script will pick up the 64 bit files and disable gstreamer support in the 32 bit build. ”
https://wiki.winehq.org/Building_Wine#Shared_WoW64
But It doesn’t work for me. Centos 7.3 (1611) 64 bit
It should be because of the missing of the `glib2-devel.i686` package.
Please check out the latest install-wine-i686-centos7.sh in git. It fixes the gstreamer problem. No “gstreamer” anymore in the non-supported component list:
configure: OpenCL 32-bit development files not found, OpenCL won’t be supported.
configure: libhal 32-bit development files not found, no legacy dynamic device support.
configure: OSS sound system found but too old (OSSv4 needed), OSS won’t be supported.
configure: libmpg123 32-bit development files not found (or too old), mp3 codec won’t be supported.
configure: libopenal 32-bit development files not found (or too old), OpenAL won’t be supported
configure: openal-soft 32-bit development files not found (or too old), XAudio2 won’t be supported
Yes you’re right!
glib2-devel.i686 not installed yet. Think I didn’t see it in your tutorial. Now seems no gstreamer issue even in wine 2.0.2. My CentOS is fresh, follow your tutorial but I must install many other packages :D
The remaining warnings only 3, which is ‘imposible’ in CentOS 7 and i’m happy to ignore:
configure: OpenCL 32-bit development files not found, OpenCL won’t be supported.
configure: libhal 32-bit development files not found, no legacy dynamic device support.
configure: OSS sound system found but too old (OSSv4 needed), OSS won’t be supported.
By the way, I installed libmpg123-devel not from nux-dextop but from epel with the different name; mpg123-devel, I think both are the same. CMIIW.
The other i686 packages required that not found, like openal, etc, I downloaded manually from here: https://buildlogs.centos.org/c7-epel/openal-soft/20160818091922/1.16.0-3.el7.i686/
I will post here the build result later! Thanks!
Build wine 2.0.2 success! It takes about 1.5 hours.
* wine 2.0.x needs gstreamer 1 instead of 0.1
* needs libudev-devel (in CentOS provided by systemd-devel)
May I ask, how to install to another fresh CentOS machine without build? Just copy and `make install`?
Excellent tutorial — THANKS!
Hi gretzware,
> Build wine 2.0.2 success!
> * wine 2.0.x needs gstreamer 1 instead of 0.1
> * needs libudev-devel (in CentOS provided by systemd-devel)
Great to know that! Thanks for the info. I will update the script to add support to 2.0.x.
> May I ask, how to install to another fresh CentOS machine without build? Just copy and `make install`?
It will likely work if: 1. install the needed packages 2. copy and `make install`. But I did not test it.
Hello. I even successfully install 2.17 development, needs libXfixes-devel
Can you help me.. for some reasons, I need try older version, but here is the warning when build Wine 1.3.x 32bit:
configure: libGLU 32-bit development files not found, GLU won’t be supported.
For previous gstreamer issue, you suggest `glib2-devel.i686` and fixes the issue. This is the similiar case. How to fix?
Thanks!
Good to know it works for 2.17 development.
For the way to find how to fix `libGLU 32-bit development files not found`, it is as follows.
Check config.log to find the reported not working libraries. For this case, search for ‘GLU’.
It shows:
The problem here is that `cannot find -lSM`. A library ‘SM’ is not properly installed.
gives:
It is likely what is needed. Install both the 64- and 32-bit versions:
# yum install libSM-devel.{x86_64,i686}Do the `configure` again in wine and the `libGLU 32-bit development files not found, GLU won’t be supported` will be gone.
Hope this helps.
Thanks for smart, correct and to the point answer! It works!
Now I know little how to read config.log
Have a nice day!
Hi,
First of all thank you for sharing this install method.
I’m getting a conflict on the install of gstreamer1-plugins-base-devel:
Transaction check error:
file /usr/lib64/gstreamer-1.0/libgstopus.so from install of gstreamer1-plugins-base-1.10.4-1.el7.x86_64 conflicts with file from package gstreamer1-plugins-bad-free-1.4.5-6.el7_3.x86_64
I can remove gstreamer-plugins-bad-free, but that will remove some other software such as totem (which I don’t use but others might).
Thanks, Randy
Updating them may make these 2 package stay together. On one system I can have both with the same versions:
For someone who want to try wine32 without build.. Try this repo https://gitlab.com/harbottle/wine32
But this Eric’s tutorial still useful for build wine64 with shared WoW64 (32 bit support)
i follow everything in this tutorial. It went smoothly but when I call wine it returns
“bash: wine: command not found”
Please help
sorry, got it to work after i move out of root access
but now i get this error when i call winecfg
winecfg
wine: created the configuration directory ‘/home/user/.wine’
err:ole:marshal_object couldn’t get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
err:ole:marshal_object couldn’t get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa}
err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
err:ole:get_local_server_stream Failed: 80004002
err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
err:ole:apartment_createwindowifneeded CreateWindow failed with error 0
err:ole:apartment_createwindowifneeded CreateWindow failed with error 0
err:ole:marshal_object couldn’t get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
err:ole:apartment_createwindowifneeded CreateWindow failed with error 14007
err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x800736b7
err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 800736b7
err:ole:get_local_server_stream Failed: 800736b7
err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
Could not load wine-gecko. HTML rendering will be disabled.
err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
Could not load wine-gecko. HTML rendering will be disabled.
wine: configuration in ‘/home/faris_ramadhan/.wine’ has been updated.
err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
please help
err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
–> It seems your X environment was not set correctly?
Hey, I’m trying to install manually but I’m getting an error saying “undefined reference to yy_scan_string”. Any idea why this would be the case?
Thanks
Some libraries may be missing. If you post all the commands/outputs/logs, others may take a look.
…or you can just use my wine32 repo.
sudo yum -y install https://harbottle.gitlab.io/wine32/7/i386/wine32-release.rpm
sudo yum -y install wine.i686
More details here:
https://gitlab.com/harbottle/wine32
Thank you, Harbottle!
As Gretzware said, this Systutorials page remains very valuable. But for someone who only needs Wine 32-bit, Harbottle’s repo is a great solution. Even registered on Gitlab because more people should star this project :)
sadly this didnt work either
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for nss-mdns which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of nss-mdns of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
–exclude nss-mdns.otherarch … this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of nss-mdns installed, but
yum can only see an upgrade for one of those architectures.
If you don’t want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of nss-mdns installed already.
You can use “yum check” to get yum show these errors.
…you can also use –setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: nss-mdns-0.14.1-7.el7.i686 != nss-mdns-0.14.1-9.el7.x86_64
Thank you, Harbottle!
As Gretzware said, this Systutorials page remains very valuable. But for someone who only needs Wine 32-bit, Harbottle’s repo is a great solution. Even registered on Gitlab because more people should star this project :)
Thank you, Harbottle!
As Gretzware said, this Systutorials page remains very valuable. But for someone who only needs Wine 32-bit, Harbottle’s repo is a great solution. Even registered on Gitlab because more people should star this project :)
This installation guide also works with the current developer wine version 4.10.0.
Regards,
L.
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for lz4 which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of lz4 of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
–exclude lz4.otherarch … this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of lz4 installed, but
yum can only see an upgrade for one of those architectures.
If you don’t want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of lz4 installed already.
You can use “yum check” to get yum show these errors.
…you can also use –setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: lz4-1.7.5-2.el7.i686 != lz4-1.8.3-1.el7_6.x86_64
We have the below error when traying to install 32 bit wine 4.0 in rhel 7.6.
configure: OpenCL 32-bit development files not found, OpenCL won’t be supported.
configure: libhal 32-bit development files not found, no legacy dynamic device support.
configure: OSS sound system found but too old (OSSv4 needed), OSS won’t be supported.
configure: libSDL2 32-bit development files not found, SDL2 won’t be supported.
configure: libcups 32-bit development files not found, CUPS won’t be supported.
configure: libkrb5 32-bit development files not found (or too old), Kerberos won’t be supported.
configure: libgssapi_krb5 32-bit development files not found (or too old), no Kerberos SSP support.
configure: libmpg123 32-bit development files not found (or too old), mp3 codec won’t be supported.
configure: libopenal 32-bit development files not found (or too old), OpenAL won’t be supported.
configure: openal-soft 32-bit development files not found (or too old), XAudio2 won’t be supported.
configure: libvulkan and libMoltenVK 32-bit development files not found, Vulkan won’t be supported.
configure: vkd3d 32-bit development files not found, Direct3D 12 won’t be supported.
configure: Finished. Do ‘make’ to compile Wine.
Thank you so much for all of your work on this. Super helpful!!!
I had to add lib-krb5, libcom_err-devel.i686, and mingw32 to the list of stuff — but other than that this worked perfectly and got me going with relative ease.
How did you install mingw32 , I tried every possible solution I was never able to install it on CentOS
Hi Erik – thanks
using Redhat – Red Hat Enterprise Linux Server release 7.7 (Maipo)
installed wine-2.0.2 using install-wine-i686-centos7.sh
objective to run a wndows 32 bit exe in Redhat VM
executed wine ATClient_2715t.exe
error wine: failed to initialize: /usr/local/lib/wine/ntdll.dll.so: cannot open
shared object file: Permission denied
The install ion was success !
Then i tried to run the a windows exe from /app/data/tools with wine which failed to initialize with /usr/local/lib/wine/ntdll.dll.so: cannot open shared object file: Permission denied
—————————————————————————————————–
sh-4.2$ file ATClient_2715t.exe
ATClient_2715t.exe: PE32 executable (GUI) Intel 80386, for MS Windows
sh-4.2$
sh-4.2$ ls -lrt
-rwxr-xr-x 1 sahoos3 gblunixdefault 9860264 Mar 1 2019 ATClient_2715t.exe
sh-4.2$ chmod 777 ATClient_2715t.exe
sh-4.2$ wine ATClient_2715t.exe
wine: failed to initialize: /usr/local/lib/wine/ntdll.dll.so: cannot open shared object file: Permission denied
———————————————————————————
sh-4.2$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.7 (Maipo)
——————————————————————————–
sh-4.2$ pwd
/app/data/tools
sh-4.2$
I don’t have a clue what’s wrong. But the
sh-4.2$part seems suggest that your shell environment may not have all environment variables wine needs? You may runenvto see whether$HOMEand others are set correctly.I am getting this error to open notepad in redhat 7.
wine notepad
0009:err:user:load_desktop_driver failed to load L”C:\\windows\\system32\\winex11.drv”
0009:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0009:err:winediag:nodrv_CreateWindow The explorer process failed to start.
i am getting this error to open wine 32
wine notepad
0009:err:user:load_desktop_driver failed to load L”C:\\windows\\system32\\winex11.drv”
0009:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0009:err:winediag:nodrv_CreateWindow The explorer process failed to start.
Please tell me how to fix it.
Eric, I had to build a docker to compile some old code that needed wine 1.8.4. Your script was perfect, installed in my docker and did the job well. Thanks so much!
Glad to know it helps!
This script did work in a VM I have built, but had an unpleasant side effect. It used quite a lot of the limited disk space. Much more than simply installing Wine packages would have. Is there a relatively simple way to cleanup after all the compiling? For example, do I need to keep all of the object files and such? What can I delete once the script is done?