On 05/18/2018 02:14 PM, Rex Dieter wrote:
Ricardo J. Barberis wrote:
El Viernes 18/05/2018 a las 00:33, Rex Dieter escribió:
Ken Taylor wrote:
On 05/16/2018 11:00 PM, Rex Dieter wrote:
Ken Taylor wrote:
I installed the wine 3 package from epel-testing this morning on a
newly installed CentOS 7.5 machine. The installation seemed to go
fine. If I may ask two questions...
Does this version of wine support 32 bit Windows programs on CentOS
7.5?
No. rhel7 (and epel7 by extension) does not support i686 arch, which
is required for win32 support
Based on my experience, rhel7 and centos7 DO support i686. epel has a
whole bunch of ...-devel.i686 packages. I have been running wine 1.8
i686 on CentOS 7 for more than two years. I am attempting to build wine
3 from source and the epel src.rpm as I write this.
I guess the question really is... is 32 bit support included in the
epel binary rpm?
No, I looked. Here's a snippet from wine.spec hinting at it:
# x86-32 parts
%ifarch %{ix86} x86_64
%if 0%{?fedora} || 0%{?rhel} <= 6
Requires: wine-core(x86-32) = %{version}-%{release}
Requires: wine-capi(x86-32) = %{version}-%{release}
Requires: wine-cms(x86-32) = %{version}-%{release}
Requires: wine-ldap(x86-32) = %{version}-%{release}
Requires: wine-twain(x86-32) = %{version}-%{release}
Requires: wine-pulseaudio(x86-32) = %{version}-%{release}
Note, only included if rhel is <=6
Then I tried to tell you why (that rhel7 has no i686 edition and epel7
has
no i686 buildroot), but you didn't believe me. Suit yourself.
There's no rhel7 i686 edition, but there is i686 support in the x86_64
edition, I beieve.
At least CentOS 7 has several i686 rpms, according to random mirror:
$ lynx -dump http://centos.eecs.wsu.edu/7/os/x86_64/Packages/ | grep -c
i686 4446
Mere existence of i686 rpms in rhel7/centos7 is does not imply either that
wine.i686 exists or that epel7 can build it. That's the point I've been
trying to make (poorly, apparently).
-- Rex
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/message/SDGDS54WWXHBGVZ6MBSGTKRSKN7WDZIE/
wine.i686 may not exist but it IS possible to build it from the epel
source rpm. I used the .spec file provided in this thread
https://www.linuxquestions.org/questions/linux-software-2/wine-3-0-3-centos-7-5-run-32-bit-windows-programs-4175629844/.
After tracking down a bunch of necessary ...devel.i686 packages, most
from epel, the command "rpmbuild -bb --target=i686 wine.spec.yes" did
the trick (where wine.spec.yes is the file provided by member yes1111).
I haev installed and run 32 bit Windows programs on the CentOS 7.5 machine.
yes1111 has also tracked down and built a boat load of dependency rpms
along with the base wine rpm. If I throw them all in a directory and
issue "yum install *" I end up with a functioning 32 bit wine environment.
The Ubuntu wine 3.0.1, as best I can tell, installs both architectures.
I can set it for 32 bit programs by:
1 - delete ~/.wine
2 - WINEARCH=win32
3 - running winecfg to build my new ~/.wine structure in 32 bit flavor.
It would be nice if both architectures could be made available in the
epel wine package although that is beyond my skill set.
Ken
Ken
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/message/4TOGZNV5EWPFO6BWSLH7CLPNAVXWXX7U/
