Wine patch to support PPC64

Started by tle, August 29, 2020, 03:19:46 AM

Previous topic - Next topic

tle

Faithful Linux enthusiast

My Raptor Blackbird

FlyingBlackbird

Fascinating!

Can somebody explain how it will be possible to execute Windows binaries via Wine on a ppc64le architecture (which has a different CPU instruction set than x86)? QEMU?

I thought Wine is "just" offering the Windows API as a wrapper around kernel/Linux calls...

jirka

Quote from: FlyingBlackbird on August 30, 2020, 05:54:49 PM
Can somebody explain how it will be possible to execute Windows binaries via Wine on a ppc64le architecture (which has a different CPU instruction set than x86)? QEMU?

No way.

It's just the winelib port: a library which allows to compile some programs which use Win API. It cannot be used  to run  x86 binaries on the POWER.
Probably sent from the sforza (a Blackbird workstation with Fedora) or the moose (a SGI O2).

ClassicHasClass

Exactly. You'd need something like Hangover to do that.

cchinicz

Quote from: ClassicHasClass on August 31, 2020, 10:53:11 PM
Exactly. You'd need something like Hangover to do that.
Hey Classic,

I've just read your article (www.talospace.com/2020/10/its-good-to-have-hangover.html) about Hangover and visited the project page (github.com/AndreRH/hangover/tree/acb911f9ad38ef835d9265b6d474092970faa4ca).

Is there a binary that I can download and test?

I read the warning about 4 vs 64K pages. I'm using Fedora 33. Is it worth trying?

Thanks

MPC7500


cchinicz

Yeah, I know. It's just that Classic wrote "loading PE binaries, which have 4K aligned sections, into a 64K page comes with [lots] of problems, so currently the best approach is to avoid that". So I asked if it was worth trying anyway.

cchinicz

BTW, once I tried to install Windows 10 on a VM using QEMU. I was a pain because it was extremely slow and frustrating because in the end the install failed. Anyway, that Windows binary iso must have compiled for 4K memory Pages but QEMU seems to have handled that, I guess.

ClassicHasClass

No, it's not going to work properly. The code doesn't currently account for that situation. I would be surprised if anything worked correctly on a 64K-paged system as written.