wine64 from Epel does not start win32 applications

Issues related to applications and software problems
woweil
Posts: 10
Joined: 2012/08/13 07:08:25
Location: Berlin Germany

wine64 from Epel does not start win32 applications

Post by woweil » 2014/07/18 19:33:43

I have installed wine64 from EPEL,
The WINEPREFIX and WINEARCH were set like this:

When I call "WINEPREFIX=/home/wow/testwine WINEARCH=win32 wineboot -i" I got the following message:
wine: created the configuration directory '/home/wow/testwine'
wine: '/home/wow/testwine' is a 32-bit installation, it cannot support 64-bit applications.

And when I invoke after this a Windows application:

wine "mp3dc220.exe" in /home/wow/testwine I get this message too:

wine: '/home/wow/testwine' is a 32-bit installation, it cannot support 64-bit applications.

But of course mp3dc220.exe is a 32bit application:

file mp3dc220.exe
mp3dc220.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed

So I do not know what else I have to do, to get run 32bit Windows-Application. If the 64bit Applications are running, I do not know. I have none.

Many thanks for your tips.

Greetings
Wolfram

RHCE7
Posts: 3
Joined: 2014/07/24 22:03:51

Re: wine64 from Epel does not start win32 applications

Post by RHCE7 » 2014/07/24 22:07:19

I have the same problem.

In CentOS 7 wine is a symlink to wine64.

# ls -la /usr/bin/wine
lrwxrwxrwx 1 root 15 июл 24 16:52 /usr/bin/wine -> /usr/bin/wine64

I don't know how to run 32 bit apps.


In CentOS 6.5 it was a 32-bit elf:

# wine --version
wine-1.6.1
# file /usr/bin/wine
/usr/bin/wine: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped

assen
Posts: 80
Joined: 2013/02/22 12:48:05
Contact:

Re: wine64 from Epel does not start win32 applications

Post by assen » 2014/07/26 21:27:46

You'll likely need a separate, 32-bit bottle for this:

prompt> WINEARCH=win32 WINEPREFIX=~/.wine-x86 winecfg
promtp> WINEPREFIX=~/.wine-x86 wine nameoftheapp.exe

WWell,

RHCE7
Posts: 3
Joined: 2014/07/24 22:03:51

Re: wine64 from Epel does not start win32 applications

Post by RHCE7 » 2014/07/29 19:50:02

assen wrote:You'll likely need a separate, 32-bit bottle for this:

prompt> WINEARCH=win32 WINEPREFIX=~/.wine-x86 winecfg
promtp> WINEPREFIX=~/.wine-x86 wine nameoftheapp.exe

WWell,
it does not work
$ WINEARCH=win32 WINEPREFIX=~/.wine-x86 winecfg
wine: created the configuration directory '/home/user/.wine-x86'
wine: '/home/user/.wine-x86' is a 32-bit installation, it cannot support 64-bit applications.
$ WINEPREFIX=~/.wine-x86 wine bin/app.exe
wine: '/home/user/.wine-x86' is a 32-bit installation, it cannot support 64-bit applications.
$ file bin/app.exe
bin/app.exe: PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows

lklaus
Posts: 6
Joined: 2014/07/26 21:23:46

Re: wine64 from Epel does not start win32 applications

Post by lklaus » 2014/07/30 18:12:16

Same for me. To me it looks like there should be some 32bit packages.

On a 64bit Fedora 20, there are
wine-capi-1.7.22-1.fc20.i686
wine-openal-1.7.22-1.fc20.i686
wine-core-1.7.22-1.fc20.i686
wine-twain-1.7.22-1.fc20.i686
wine-ldap-1.7.22-1.fc20.i686
wine-cms-1.7.22-1.fc20.i686
wine-pulseaudio-1.7.22-1.fc20.i686

I think, at least a wine-core in 32bit would be necessary, which installs lot of libraries into /usr/lib, instead of /usr/lib64. But I have to admit, I have not yet looked into the RHEL/CENTOS7 64bit technology for supporting 32bit applications. Standard libraries are in .i686 and .x86_64. So probably for wine this is needed too?

Klaus

nutznboltz
Posts: 25
Joined: 2010/06/08 18:32:43

Re: wine64 from Epel does not start win32 applications

Post by nutznboltz » 2014/08/04 14:30:15

Related bug report:

https://bugzilla.redhat.com/show_bug.cgi?id=1117422

Related post (32-bit Springdale Linux)

viewtopic.php?f=47&t=47473

So how long before somebody rebuilds EPEL on 32-bit Springdale Linux 7?

m3tti
Posts: 4
Joined: 2014/07/31 08:26:01

Re: wine64 from Epel does not start win32 applications

Post by m3tti » 2014/08/05 10:53:10

Hi there,

my solution for now is:

- grep the PlayOnLinux Fedora Package at http://rpm.playonlinux.com/playonlinux- ... noarch.rpm
- install all i686 libraries

Code: Select all

yum install glibc.i686 alsa-lib.i686 libXv.i686 libXScrnSaver.i686 libSM.i686 libXi.i686 libXrender.i686 libXrandr.i686 freetype.i686 fontconfig.i686 zlib.i686 glib2.i686 libstdc++.i686
- start PlayOnLinux

Thats all and it works fine. You don't even needed to install wine from EPEL. PlayOnLinux greps the latest wine build.

Best regards

nutznboltz
Posts: 25
Joined: 2010/06/08 18:32:43

Re: wine64 from Epel does not start win32 applications

Post by nutznboltz » 2014/08/06 13:41:19

Yes, I was able to install the 32-bit RPMs from CentOS repos;

Code: Select all

yum install glibc.i686 alsa-lib.i686 libXv.i686 libXScrnSaver.i686 libSM.i686 libXi.i686 libXrender.i686 libXrandr.i686 freetype.i686 fontconfig.i686 zlib.i686 glib2.i686 libstdc++.i686
Then navigate to the page where the latest PlayOnLinux Yum repo RPM is located: http://rpm.playonlinux.com/

Then install the repo RPM on that page

Then I tried to install the playonlinux.noarch RPM from the PlayOnLinux repo.

It failed because it has dependencies on wine RPMs which did not exist in any repos the CentOS 7 system had configured. If I added the epel repo it tries to get them from there but they are 64-bit.

m3tti
Posts: 4
Joined: 2014/07/31 08:26:01

Re: wine64 from Epel does not start win32 applications

Post by m3tti » 2014/08/06 19:12:42

nutznboltz wrote:Yes, I was able to install the 32-bit RPMs from CentOS repos;

Code: Select all

yum install glibc.i686 alsa-lib.i686 libXv.i686 libXScrnSaver.i686 libSM.i686 libXi.i686 libXrender.i686 libXrandr.i686 freetype.i686 fontconfig.i686 zlib.i686 glib2.i686 libstdc++.i686
Then navigate to the page where the latest PlayOnLinux Yum repo RPM is located: http://rpm.playonlinux.com/

Then install the repo RPM on that page

Then I tried to install the playonlinux.noarch RPM from the PlayOnLinux repo.

It failed because it has dependencies on wine RPMs which did not exist in any repos the CentOS 7 system had configured. If I added the epel repo it tries to get them from there but they are 64-bit.
Yeah indeed i've looked that over after my post. You have to install the wine version on the epel repo. But afterwards playonlinux will download a newer version of wine and use that instead. So just go ahead and install the 64bit wine and use playonlinux it'll do exactly what it needs.

nutznboltz
Posts: 25
Joined: 2010/06/08 18:32:43

Re: wine64 from Epel does not start win32 applications

Post by nutznboltz » 2014/08/07 14:24:44

Thanks for explaining PlayOnLinux. I tried it but it crashed when I tried to install the program I wanted which was not on the PlayOnLinux list.

Meanwhile I recompiled the EPEL wine RPMs on Springdale EL7 (Verona) 32-bit and it runs EditPad Lite.

The tricky part was that Michael Cronenworth's modifications to wine.spec hard-coded "EL7 == 64-bits" in a few locations. I had to get rid of such nonsense.

Screenshot:
https://drive.google.com/file/d/0ByWsBZ ... sp=sharing

I copied the 32-bit wine RPMs to CentOS 7 64-bit and used createrepo to enable yum installation. The only snag is both

Code: Select all

yum install wine.i686
and

Code: Select all

yum install wine-wow.i686
where needed

Post Reply

Return to “CentOS 7 - Software Support”