Hello! Jan Nieuwenhuizen <jann...@gnu.org> skribis:
> I pushed an initial wip-arm-bootstrap that builds up to tcc-boot: > > ./pre-inst-env guix build -e '(@@ (gnu packages commencement) tcc-boot)' > > > Danny did a terrific job on armhf-linux support for GNU Mes and we are > getting close to release v0.23. What's known to be missing is "setjmp" > support for tcc/gcc. And, of course, for the Reduced binary seed > bootstrap to work on ARM! Woohoo, thumbs up for this great milestone, hackers! 🎉 > Anyway, the problem I'm looking at now is that while tcc-boot builds on > an ARM box, it does not build on aarch64-linux, i.e. this > > ./pre-inst-env guix build --system=armhf-linux \ > -e '(@@ (gnu packages commencement) tcc-boot0)' > > fails on overdrive1. That’s “interesting”. Did you eventually find a lead? > configure: error: 'mescc' failed to compile conftest.c. > Backtrace: > In unknown file: > ?: 19 [apply-smob/1 #<catch-closure 410f30>] > [..] > In gash/shell.scm: > 165: 1 [sh:exec-let () "./conftest" "triplet"] > In unknown file: > ?: 0 [execle "./conftest" # "./conftest" ...] > > ERROR: In procedure execle: > ERROR: In procedure execle: No such file or directory Looks like the ELF interpreter on ‘conftest’ might be wrong? Thanks for the update, it’s exciting! Ludo’.
