This was causing problems in a typical use case of piping stdout/stderr to another application. So if FEXInterpreter was started, with stdout piped to another application, and FEXServer wasn't running so a new instance needed to be started. FEXServer would write a null to every pipe then close it. This includes the stdout that is being piped to the new application! This writing was legacy behaviour before FEX was properly listening to POLLHUP and is no longer necessary. Just remove the writing completely to fix this issue. Easiest test case was just `./Bin/FEXInterpreter `which ls` / | xxd | head -n 3` Returned: ``` $ ./Bin/FEXInterpreter `which ls` / | xxd | head -n 3 00000000: 0000 0000 6269 6e0a 6269 6e2e 7573 722d ....bin.bin.usr- 00000010: 6973 2d6d 6572 6765 640a 626f 6f74 0a64 is-merged.boot.d 00000020: 6576 0a65 7463 0a68 6f6d 650a 6c69 620a ev.etc.home.lib. ``` That first null shouldn't be there.
FEX - Fast x86 emulation frontend
FEX allows you to run x86 and x86-64 binaries on an AArch64 host, similar to qemu-user and box86. It has native support for a rootfs overlay, so you don't need to chroot, as well as some thunklibs so it can forward things like GL to the host. FEX presents a Linux 5.0+ interface to the guest, and supports only AArch64 as a host. FEX is very much work in progress, so expect things to change.
Quick start guide
For Ubuntu 20.04, 21.04, 21.10, 22.04
Execute the following command in the terminal to install FEX through a PPA.
curl --silent https://raw.githubusercontent.com/FEX-Emu/FEX/main/Scripts/InstallFEX.py --output /tmp/InstallFEX.py && python3 /tmp/InstallFEX.py && rm /tmp/InstallFEX.py
This command will walk you through installing FEX through a PPA, and downloading a RootFS for use with FEX.
Ubuntu PPA is updated with our monthly releases.
For everyone else
Please see Building FEX.
Getting Started
FEX has been tested to build and run on ARMv8.0+ hardware. ARMv7 hardware will not work. Expected operating system usage is Linux. FEX has been tested with Ubuntu 20.04, 20.10, and 21.04. Also Arch Linux.
On AArch64 hosts the user MUST have an x86-64 RootFS Creating a RootFS.
Navigating the Source
See the Source Outline for more information.
Building FEX
Follow the guide on the official FEX-Emu Wiki here.
RootFS generation
AArch64 hosts require a rootfs for running applications. Follow the guide on the wiki page for seeing how to set up the rootfs from scratch https://wiki.fex-emu.com/index.php/Development:Setting_up_RootFS