Results from using qemu-user-static for trying to build other architectures

[Adolf Belka <adolf.belka@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]

Hi All,

When ever I do a package update on something like samba then I normally only provide the rootfile for x86_64 and then others of you have to notice that and do the build for aarch64 or riscv64.

So I thought I would have another go at using qemu-user-static to test out building samba for aarch64.

I installed qemu-user-static and qemu-user-static-binfmt and then started a build with target-aarch64.

Unfortunately after 68 hours of build time the system is still only at the start of the build-ipfire and should reach the rust build section in the next hour or two.

Based on this then a full build could be around 8 or 9 days running 24/7.

The computer I am using for this has a Ryzen 7 5700G processor with 32G of memory so it seems a reasonably powerful system. With the native x86_64 architecture the build is around 2 to 2.5 hours.

For a lot of the packages when it is building the aarch64 the 16 CPU cores are 100% utilised.


I know that it is said that a build using qemu-user-static will be slower due to the emulation but is the sort of speed I am experiencing what you would expect or am I doing something wrong.

With the above sort of performance I cannot run the aarch64 and riscv64 architectures as the computer would just be unavailable for other things such as building update packages and trying to fix bugs.

Thanks for any feedback.

Regards,

Adolf.