Hi Pierre, FYI, it looks like you included bug-guix@gnu.org in the CC list of your last email. If you do that, I believe it will create a new bug report, which may not be what you intended to do. Pierre Langlois writes: > I'm afraid I don't have any new insight if this is an issue or just > working as intended. Given we have a limited bandwidth to address this > thoroughly, would it make sense to apply a temporary work-around in the > mean time? I'd be good for at least guix to build on aarch64 in the 1.4 > release. > > I have the attached patch in my tree for instance (along with an update > of the guix package), and I've not noticed any issues on a rockpro64, > running cgit, DHCP and dnsmasq. That's just anecdotal :-), but I'm also > thinking if we unblock the guix package then the farm might catch other > issues that could help getting to the bottom of this. > > WDYT? I agree with you. That said, I don't personally run any aarch64-linux machines, and I don't plan to investigate the aarch64-linux issue further right now. Although I will defer to anyone who actually runs aarch64-linux and knows better, at the moment to me it seems reasonable to commit a patch like the one you've proposed in order to ensure that the "guix" package builds successfully on that platform for the 1.4.0 release. The fact that you have successfully built and used various pieces of software on aarch64-linux with this patch suggests that maybe the current behavior is OK, after all. I've made some rather trivial modifications to your patch, mainly to make it conform to our required ChangeLog format. If nobody has further comments, I will commit the attached version to master in about 24 hours. -- Chris PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836