I repost my reply for the list: Hello, I don't know any magic trick to do what you asked; What I usually do is to use distcc on the guest, and on the host run distccd-armv8. This way you can speed up compilation, though I can't tell you exactly by how much. You are not using native compilation though but cross-compilation this way. You can look at the distcc page on the wiki to know how to compile with distcc with or without makepkg. distccd-alarm-armv8 is available on the AUR. Cheers Le dim. 2 juin 2024 à 21:53, SET <set@xxxxxxxxxx> a écrit : > > Hello, > > I followed the instructions at > > https://nerdstuff.org/posts/ > 2020/2020-003_simplest_way_to_create_an_arm_chroot/ > > and successfully chroot'ed in the generic aarch64 image available at > > https://archlinuxarm.org/platforms/armv8/generic > > on a host running x86_64 arch. > > I installed qemu-user-static and qemu-user-static-binfmt, restarted systemd- > binfmt as advised and the chroot worked using arch-chroot. > > The slow execution speed has been surprising, I would say roughly 10 times > slower than on native x86_64 (building a library, 53 mins instead of < 5). I > understand that there's an overhead translation instructions for another > architecture. qemu is always advertised as a *fast* emulator, so I'm wondering > if I'm missing something. > > I wish to know if there's some way to speed up execution time in the chroot, > some magic configuration to apply. That's my first attempt in this direction. > > Thank you for any input. > > >
