Hi Kevin and EPEL,
Is there any sign of EPEL 7 support for Wine 32 yet? The lack of Wine 32 is keeping me on SL 6.6 and it is starting to drive me nuts!
EPEL: think of the guilt you would feel if I get stuck in an insane asylums over the lack of wine 32 support! Seriously, the guilt would haunt you to the end of your days. Okay, maybe not, but still ...
Many thanks, -T
Hey, I had to try. If guilt doesn't work, I am really good at insincere compliments too.
On Tue, 05 May 2015 23:28:47 -0700 ToddAndMargo ToddAndMargo@zoho.com wrote:
Hi Kevin and EPEL,
Is there any sign of EPEL 7 support for Wine 32 yet? The lack of Wine 32 is keeping me on SL 6.6 and it is starting to drive me nuts!
I have 0 idea. ;) I don't maintain wine or use it...
kevin
On 6 May 2015 at 00:28, ToddAndMargo ToddAndMargo@zoho.com wrote:
Hi Kevin and EPEL,
Is there any sign of EPEL 7 support for Wine 32 yet? The lack of Wine 32 is keeping me on SL 6.6 and it is starting to drive me nuts!
EPEL: think of the guilt you would feel if I get stuck in an insane asylums over the lack of wine 32 support! Seriously, the guilt would haunt you to the end of your days. Okay, maybe not, but still ...
Sadly it isn't possible in EPEL. There are not enough of the i686 libraries available to compile all the tools needed. It will require people actually doing the work to making an i686 CentOS or Scientific Linux but that only seems possible if the glibc/kernel/some other tools are not the same as in x86_64 and it would require people to actually do the work which no one has shown much effort in wanting to do.
The only solution I could see is using the Fedora19 x86_32 wine and tools.
Many thanks, -T
Hey, I had to try. If guilt doesn't work, I am really good at insincere compliments too.
--
Computers are like air conditioners. They malfunction when you open windows
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On 05/06/2015 09:31 AM, Stephen John Smoogen wrote:
On 6 May 2015 at 00:28, ToddAndMargo ToddAndMargo@zoho.com wrote:
Hi Kevin and EPEL,
Is there any sign of EPEL 7 support for Wine 32 yet? The lack of Wine 32 is keeping me on SL 6.6 and it is starting to drive me nuts!
EPEL: think of the guilt you would feel if I get stuck in an insane asylums over the lack of wine 32 support! Seriously, the guilt would haunt you to the end of your days. Okay, maybe not, but still ...
Sadly it isn't possible in EPEL. There are not enough of the i686 libraries available to compile all the tools needed. It will require people actually doing the work to making an i686 CentOS or Scientific Linux but that only seems possible if the glibc/kernel/some other tools are not the same as in x86_64 and it would require people to actually do the work which no one has shown much effort in wanting to do.
Hi Steven,
Does this help?
https://www.centos.org/forums/viewtopic.php?f=48&t=49542
Seems like most of the thinking has already been done.
Many thanks, -T
The only solution I could see is using the Fedora19 x86_32 wine and tools.
Wine works great on FC 21. But I have to use SL 6.x in my office so I can platform my server's out there.
Many thanks, -T
Hey, I had to try. If guilt doesn't work, I am really good at insincere compliments too.
Have I mentioned that you have the best ... Wait, you will have to support Wine 32 before you get any of my insincere compliments. That is if I don't wind up in the loony bin first. :'(
--
Computers are like air conditioners. They malfunction when you open windows
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On 6 May 2015 at 18:21, ToddAndMargo ToddAndMargo@zoho.com wrote:
On 05/06/2015 09:31 AM, Stephen John Smoogen wrote:
On 6 May 2015 at 00:28, ToddAndMargo ToddAndMargo@zoho.com wrote:
Hi Kevin and EPEL,
Is there any sign of EPEL 7 support for Wine 32 yet? The lack of Wine 32 is keeping me on SL 6.6 and it is starting to drive me nuts!
EPEL: think of the guilt you would feel if I get stuck in an insane asylums over the lack of wine 32 support! Seriously, the guilt would haunt you to the end of your days. Okay, maybe not, but still ...
Sadly it isn't possible in EPEL. There are not enough of the i686 libraries available to compile all the tools needed. It will require people actually doing the work to making an i686 CentOS or Scientific Linux but that only seems possible if the glibc/kernel/some other tools are not the same as in x86_64 and it would require people to actually do the work which no one has shown much effort in wanting to do.
Hi Steven,
Does this help?
https://www.centos.org/forums/viewtopic.php?f=48&t=49542
Seems like most of the thinking has already been done.
Not really. That works well for building it yourself and you should follow those instructions for your own benefit. It doesn't work in our build system for various reasons I can give hand-wavey answers to but Dennis Gilmore or another Release Engineer could answer in depth if you need. [And from my last asking about this.. it isn't something that can be fixed simply.]
On Wednesday, May 06, 2015 06:53:54 PM Stephen John Smoogen wrote:
On 6 May 2015 at 18:21, ToddAndMargo ToddAndMargo@zoho.com wrote:
On 05/06/2015 09:31 AM, Stephen John Smoogen wrote:
On 6 May 2015 at 00:28, ToddAndMargo ToddAndMargo@zoho.com wrote:
Hi Kevin and EPEL,
Is there any sign of EPEL 7 support for Wine 32 yet? The lack of Wine 32 is keeping me on SL 6.6 and it is starting to drive me nuts!
EPEL: think of the guilt you would feel if I get stuck in an insane asylums over the lack of wine 32 support! Seriously, the guilt would haunt you to the end of your days. Okay, maybe not, but still ...
Sadly it isn't possible in EPEL. There are not enough of the i686 libraries available to compile all the tools needed. It will require people actually doing the work to making an i686 CentOS or Scientific Linux but that only seems possible if the glibc/kernel/some other tools are not the same as in x86_64 and it would require people to actually do the work which no one has shown much effort in wanting to do.
Hi Steven,
Does this help?
https://www.centos.org/forums/viewtopic.php?f=48&t=49542
Seems like most of the thinking has already been done.
Not really. That works well for building it yourself and you should follow those instructions for your own benefit. It doesn't work in our build system for various reasons I can give hand-wavey answers to but Dennis Gilmore or another Release Engineer could answer in depth if you need. [And from my last asking about this.. it isn't something that can be fixed simply.]
a few issues, the biggest one is that koji enforces single arch in the buildroots. so we can only build i686 in a i686 chroot. since we do not have enough i686 content to enable building i686 its not possible that route. the other way to try and do it would be to cross build the world so that we have x86_64 rpms with 32 bit content in them. that would require exeptions to the packaging guidelines, and somoene to write new specs for every package needed and to get them through review. in the end you would have to use a non rhel evironment and you would have say glibc32 openssl32 etc x86_64 rpms that means a massive support burden. without Red Hat providing full 32 bit trees its just not a realistic option to support any 32 bit builds for epel7
Dennis
On 05/07/2015 06:17 AM, Dennis Gilmore wrote:
On Wednesday, May 06, 2015 06:53:54 PM Stephen John Smoogen wrote:
On 6 May 2015 at 18:21, ToddAndMargo ToddAndMargo@zoho.com wrote:
On 05/06/2015 09:31 AM, Stephen John Smoogen wrote:
On 6 May 2015 at 00:28, ToddAndMargo ToddAndMargo@zoho.com wrote:
Hi Kevin and EPEL,
Is there any sign of EPEL 7 support for Wine 32 yet? The lack of Wine 32 is keeping me on SL 6.6 and it is starting to drive me nuts!
EPEL: think of the guilt you would feel if I get stuck in an insane asylums over the lack of wine 32 support! Seriously, the guilt would haunt you to the end of your days. Okay, maybe not, but still ...
Sadly it isn't possible in EPEL. There are not enough of the i686 libraries available to compile all the tools needed. It will require people actually doing the work to making an i686 CentOS or Scientific Linux but that only seems possible if the glibc/kernel/some other tools are not the same as in x86_64 and it would require people to actually do the work which no one has shown much effort in wanting to do.
Hi Steven,
Does this help?
https://www.centos.org/forums/viewtopic.php?f=48&t=49542
Seems like most of the thinking has already been done.
Not really. That works well for building it yourself and you should follow those instructions for your own benefit. It doesn't work in our build system for various reasons I can give hand-wavey answers to but Dennis Gilmore or another Release Engineer could answer in depth if you need. [And from my last asking about this.. it isn't something that can be fixed simply.]
a few issues, the biggest one is that koji enforces single arch in the buildroots. so we can only build i686 in a i686 chroot. since we do not have enough i686 content to enable building i686 its not possible that route. the other way to try and do it would be to cross build the world so that we have x86_64 rpms with 32 bit content in them. that would require exeptions to the packaging guidelines, and somoene to write new specs for every package needed and to get them through review. in the end you would have to use a non rhel evironment and you would have say glibc32 openssl32 etc x86_64 rpms that means a massive support burden. without Red Hat providing full 32 bit trees its just not a realistic option to support any 32 bit builds for epel7
Dennis
Any sign of Red Hat changing their ways? Or are they just sick and tired of 32 bit?
Am 07.05.2015 um 21:58 schrieb ToddAndMargo:
Any sign of Red Hat changing their ways? Or are they just sick and tired of 32 bit?
i686 is dead - there is no RHEL7 for i686 at all
the last non x86_64 i faced was 5 years ago and frankly the whole linux stack would be much more tiny without the old code and could be optimized for mordern and relevant CPU's
On 05/07/2015 01:02 PM, Reindl Harald wrote:
Am 07.05.2015 um 21:58 schrieb ToddAndMargo:
Any sign of Red Hat changing their ways? Or are they just sick and tired of 32 bit?
i686 is dead - there is no RHEL7 for i686 at all
the last non x86_64 i faced was 5 years ago and frankly the whole linux stack would be much more tiny without the old code and could be optimized for mordern and relevant CPU's
Do you have any special method on how to run Wine 32?
Am 08.05.2015 um 21:09 schrieb ToddAndMargo:
On 05/07/2015 01:02 PM, Reindl Harald wrote:
Am 07.05.2015 um 21:58 schrieb ToddAndMargo:
Any sign of Red Hat changing their ways? Or are they just sick and tired of 32 bit?
i686 is dead - there is no RHEL7 for i686 at all
the last non x86_64 i faced was 5 years ago and frankly the whole linux stack would be much more tiny without the old code and could be optimized for mordern and relevant CPU's
Do you have any special method on how to run Wine 32?
i don't have a real need for wine and if there is something which needs windows on recent hardware it's no problem to setup a virtual machine
On 05/08/2015 08:34 PM, Reindl Harald wrote:
Am 08.05.2015 um 21:09 schrieb ToddAndMargo:
On 05/07/2015 01:02 PM, Reindl Harald wrote:
Am 07.05.2015 um 21:58 schrieb ToddAndMargo:
Any sign of Red Hat changing their ways? Or are they just sick and tired of 32 bit?
i686 is dead - there is no RHEL7 for i686 at all
the last non x86_64 i faced was 5 years ago and frankly the whole linux stack would be much more tiny without the old code and could be optimized for mordern and relevant CPU's
Do you have any special method on how to run Wine 32?
i don't have a real need for wine and if there is something which needs windows on recent hardware it's no problem to setup a virtual machine
Hi Reindl,
I have 14 VM's (although I usually only run two at a time). They can be a pain in the neck at times. The hassle of having a window inside a window with all its own controls does cut down on productivity. Coherence (floating windows) would help a lot.
https://bugs.freedesktop.org/show_bug.cgi?id=39238
I have used Coherence on Apple under Parallels and I have to tell you, it is sweet. (Not sweet enough for me to switch Apple, mind you. I work on Apple, but they do drive me a bit crazy at times)
My goal is to be able to run everything I need from my Linux base (host) system and relegate the VM's to research.
-T
On 05/07/2015 01:02 PM, Reindl Harald wrote:
Am 07.05.2015 um 21:58 schrieb ToddAndMargo:
Any sign of Red Hat changing their ways? Or are they just sick and tired of 32 bit?
i686 is dead - there is no RHEL7 for i686 at all
Hi Reindl,
https://access.redhat.com/solutions/509373 RHEL 7 will continue to provide selected libraries in both 32-bit and 64-bit, allowing 32-bit applications to run in the 64-bit RHEL 7 OS environment. This functionality also exists for RHEL 5 & 6 as documented in the knowledge article: How to install 32-bit packages on a 64-bit system
This is not a case of "can't" but "don't want to". Can't say I blame them, but it doesn't help me with Wine 32.
the last non x86_64 i faced was 5 years ago and frankly the whole linux stack would be much more tiny without the old code and could be optimized for mordern and relevant CPU's
Wine 32 is my only 32 app I have left since I purchased Qoppa's PDF Studio Pro (worth every cent, by the way). Accationally, I still have to use 32 bit only Acrobat Reader for Dynamic XFA forms (they are a pain in the neck).
Maybe at some point, if Coherence gets any traction under KVM maybe we can work around the 32 bit problem with RHEL 7 https://bugs.freedesktop.org/show_bug.cgi?id=39238
-T
So I know this thread has been silent for a long while, but since the last post was before the CentOS AltArch SIG announcement of CentOS 7 32-bit has the situation changed?
https://lists.centos.org/pipermail/centos-announce/2015-October/021430.html
epel-devel@lists.fedoraproject.org