On 2019-06-10, Jan Nieuwenhuizen wrote: > Vagrant Cascadian writes: >> Mes itself still fails to build ... >> configure fails to detect nyacc. It may be an issue >> with multi-arch paths (e.g. /usr/lib/guile/2.2 >> vs. /usr/lib/x86_64-linux-gnu/guile/2.2). > > Oops, that looks like a bug, thanks. I hope it's harmless...
The configure script still fails to detect nyacc (with version 0.86.0, 0.86.9, 0.92.0, 0.93.0 or 0.94.0): checking for nyacc [0.86.0]... command[11]: ("/usr/bin/guile-2.2 -c '(use-modules (nyacc lalr)) (display *nyacc-version*)'" "--version") => [] no When I run the command from the commandline: $ /usr/bin/guile-2.2 -c '(use-modules (nyacc lalr)) (display *nyacc-version*)' 0.94.0 Same with any of the other versions of nyacc... So not sure why ./configure is getting an empty result... how is configure passing the "--version" argument? >> Will need to do some better troubleshooting later... but this appears to >> be the last build failure i tried based on the wip branch: >> >> ../pre-inst-env mescc -m 64 -c -D HAVE_CONFIG_H=1 -I include -I >> ../include -I ../include/linux/x86_64 -static -o crt1.o >> ../lib/linux/x86_64-mes-mescc/crt1.c >> unhandled exception:unbound-variable:(move-specl-attr) >> Backtrace: >> /<<PKGBUILDDIR>>/scripts/mescc: line 56: 24904 Segmentation fault >> ${SCHEME-$MES} --no-auto-compile -e main -L /usr/share/guile/site/2.2 -C >> /usr/lib/guile/2.2/site-ccache $bindir/mescc.scm $sep "$@" >> make[1]: *** [GNUmakefile:95: build] Error 139 > > This could be a problem with Nyacc 0.93.0, find a patch attached for > that. Patch seems to have fixed that issue. After some aggressive patching for /bin/sh -> /bin/bash and using bash -x, it manages to get further, but it still fails building libmes: + trace 'CC lib/libmes.c' /usr/bin/gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -D POSIX=1 -D WITH_GLIBC=1 -D POSIX=1 -D WITH_GLIBC=1 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -o lib/libmes.o lib/libmes.c + echo ' CC lib/libmes.c' CC lib/libmes.c + shift + eval /usr/bin/gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -D POSIX=1 -D WITH_GLIBC=1 -D POSIX=1 -D WITH_GLIBC=1 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -o lib/libmes.o lib/libmes.c '>>build.log' '2>&1' ++ /usr/bin/gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -D POSIX=1 -D WITH_GLIBC=1 -D POSIX=1 -D WITH_GLIBC=1 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -o lib/libmes.o lib/libmes.c make[1]: *** [GNUmakefile:83: build] Error 1 make[1]: Leaving directory '/<<PKGBUILDDIR>>' dh_auto_build: make -j4 returned exit code 2 make: *** [debian/rules:9: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 I also tried without the hardening build flags, but no real difference. live well, vagrant