WARNING: do not install manjaro-arm-qemu-static

[aaspectre]

If you install this package on Manjaro as required by some qemu+wine x86 tutorials on rpi, you will break your system and have to recover through chroot.

If you tend to follow RPI tutorials, or attempt to, to accomplish things, this one can have some bad consequences.
I'm not familiar with it so obviously as a rule don't run stuff if you don't know what it does, but I have been doing that a lot on PBP. It somehow made the system act like every binary was the wrong architecture, so not even basic commands like ls, cd, etc worked immediately after install.

[astr0baby]

If you install this package on Manjaro as required by some qemu+wine x86 tutorials on rpi, you will break your system and have to recover through chroot.

Always compile qemu from source

[aaspectre]

Always compile qemu from source

I had done, but I wasn't exactly sure what a particular wine x86 on rpi tutorial was calling for when it wanted me to cp a qemu-static binary from /usr/bin/ into a debootstrap, so I figured what could be the harm? Apparently, the immediate ceasing of literally all functionality. I guess this package will actually somehow get your system to run everything through qemu such that they are the wrong architecture despite being the right architecture? I'm still not sure what even happened,

If you want to take a look:
https://www.novaspirit.com/2019/04/15/run-x86-arm/

I'm still very keen on the idea of running x86 wine for some basic windows stuff on my PBP in more seamless way than a KVM, so if you have any suggestions or input, that'd be appreciated.

[astr0baby]

Always compile qemu from source

I had done, but I wasn't exactly sure what a particular wine x86 on rpi tutorial was calling for when it wanted me to cp a qemu-static binary from /usr/bin/ into a debootstrap, so I figured what could be the harm? Apparently, the immediate ceasing of literally all functionality. I guess this package will actually somehow get your system to run everything through qemu such that they are the wrong architecture despite being the right architecture? I'm still not sure what even happened,

If you want to take a look:
https://www.novaspirit.com/2019/04/15/run-x86-arm/

I'm still very keen on the idea of running x86 wine for some basic windows stuff on my PBP in more seamless way than a KVM, so if you have any suggestions or input, that'd be appreciated.

Let me tell you a little secret Windows 10 arm64 is big part x86 (32bit) code and arm64 .. so it natively runs most apps that are x86 32bit .... Windows 10 arm64 runs quite well under accelerated qemu-system-aarch64 via KVM, all you need for good work is a USB network card for Qemu passthrough and connect to the VM over network with RDP ...

If you want to run Wine x86 stuff have a look at this project called Hangover https://github.com/AndreRH/hangover its designed for arm64

[the_hiacer]

Always compile qemu from source

I had done, but I wasn't exactly sure what a particular wine x86 on rpi tutorial was calling for when it wanted me to cp a qemu-static binary from /usr/bin/ into a debootstrap, so I figured what could be the harm? Apparently, the immediate ceasing of literally all functionality. I guess this package will actually somehow get your system to run everything through qemu such that they are the wrong architecture despite being the right architecture? I'm still not sure what even happened,

If you want to take a look:
https://www.novaspirit.com/2019/04/15/run-x86-arm/

I'm still very keen on the idea of running x86 wine for some basic windows stuff on my PBP in more seamless way than a KVM, so if you have any suggestions or input, that'd be appreciated.

Let me tell you a little secret Windows 10 arm64 is big part x86 (32bit) code and arm64 .. so it natively runs most apps that are x86 32bit .... Windows 10 arm64 runs quite well under accelerated qemu-system-aarch64 via KVM, all you need for good work is a USB network card for Qemu passthrough and connect to the VM over network with RDP ...

If you want to run Wine x86 stuff have a look at this project called Hangover https://github.com/AndreRH/hangover  its designed for arm64

So this is what Microsoft is doing with its latest Surface Pro X. It works, but terribly slow.

---

Always compile qemu from source

I had done, but I wasn't exactly sure what a particular wine x86 on rpi tutorial was calling for when it wanted me to cp a qemu-static binary from /usr/bin/ into a debootstrap, so I figured what could be the harm? Apparently, the immediate ceasing of literally all functionality. I guess this package will actually somehow get your system to run everything through qemu such that they are the wrong architecture despite being the right architecture? I'm still not sure what even happened,

If you want to take a look:
https://www.novaspirit.com/2019/04/15/run-x86-arm/

I'm still very keen on the idea of running x86 wine for some basic windows stuff on my PBP in more seamless way than a KVM, so if you have any suggestions or input, that'd be appreciated.

Let me tell you a little secret Windows 10 arm64 is big part x86 (32bit) code and arm64 .. so it natively runs most apps that are x86 32bit .... Windows 10 arm64 runs quite well under accelerated qemu-system-aarch64 via KVM, all you need for good work is a USB network card for Qemu passthrough and connect to the VM over network with RDP ...

If you want to run Wine x86 stuff have a look at this project called Hangover https://github.com/AndreRH/hangover  its designed for arm64

So this is what Microsoft is doing with its latest Surface Pro X. It works, but terribly slow.