From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Results from using qemu-user-static for trying to build other architectures Date: Mon, 24 Jun 2024 13:54:50 +0200 Message-ID: <85774e8f-f4e6-4586-ae17-47385d1256f9@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4147648206757142056==" List-Id: --===============4147648206757142056== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 an= d do the build for aarch64 or riscv64. So I thought I would have another go at using qemu-user-static to test out bu= ilding samba for aarch64. I installed qemu-user-static and qemu-user-static-binfmt and then started a b= uild with target-aarch64. Unfortunately after 68 hours of build time the system is still only at the st= art of the build-ipfire and should reach the rust build section in the next h= our 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 me= mory so it seems a reasonably powerful system. With the native x86_64 archite= cture 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 ar= e 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 e= xpect or am I doing something wrong. With the above sort of performance I cannot run the aarch64 and riscv64 archi= tectures as the computer would just be unavailable for other things such as b= uilding update packages and trying to fix bugs. Thanks for any feedback. Regards, Adolf. --===============4147648206757142056==--