armhf and riscv64 build failures on Debian

[Vagrant Cascadian]

As seen on IRC!

mes no longer builds successfully on Debian armhf, segfaulting during
the build with 0.25 and 0.26:

  https://buildd.debian.org/status/logs.php?pkg=mes&arch=armhf
  
https://buildd.debian.org/status/fetch.php?pkg=mes&arch=armhf&ver=0.26-1&stamp=1704511792&raw=0

+ /<<PKGBUILDDIR>>/bin/mes --no-auto-compile -e main -L 
/usr/share/guile/site/3.0 -C /usr/lib/guile/3.0/site-ccache 
/<<PKGBUILDDIR>>/scripts/mescc.scm -- -m 32 -c -D HAVE_CONFIG_H=1 -I ../lib -I 
../include -I ../include -I include -v -static -nostdinc -nostdlib -fno-builtin 
-marm -o crt1.o crt1.c
/<<PKGBUILDDIR>>/scripts/mescc: line 69: 3327682 Segmentation fault      
${SCHEME-$MES} --no-auto-compile -e main -L /usr/share/guile/site/3.0 -C 
/usr/lib/guile/3.0/site-ccache $bindir/mescc.scm $sep "$@"
+ test -f .log

FWIW, it is built using --with-bootstrap.


On riscv64 the build is mostly sucessful, minus a couple pesky test
suites:

  https://buildd.debian.org/status/logs.php?pkg=mes&arch=riscv64
  
https://buildd.debian.org/status/fetch.php?pkg=mes&arch=riscv64&ver=0.26-1&stamp=1704532404&raw=0

␛[0;31mFAIL␛[m: lib/tests/scaffold/68-truncate-shift.c
␛[0;31mFAIL␛[m: lib/tests/setjmp/80-setjmp.c

At some point I also tried building riscv64 with m2-planet, though I
think it failed the same tests.


Thanks for all your messing around!


live well,
  vagrant

signature.asc
Description: PGP signature