On 2019-02-13, Jan Nieuwenhuizen wrote:
> I have resurrected the debian package descriptions for Nyacc,
> MesCC-tools and Mes, and updated them to the latest versions.
I made another pass at the Debian packaging needed for Mes.
mescc-tools 0.6.1 builds fine for me:
https://salsa.debian.org/vagrant/mescc-tools
Upstream nyacc 0.86.0, 0.86.9 and 0.92.0 all build fine for me:
https://salsa.debian.org/vagrant/nyacc
There are two branches wip/debian/master-0.86.x and
wip/debian/master-0.92.x.
Mes itself still fails to build, but I updated to 0.19, and made a
branch based off of janneke's wip branch as well
(debian/master-wip). 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).
Many of the '#! /bin/sh' scripts contain bashisms which may not be
compatible with Debian's (usual) /bin/sh, dash after a quick check with
"checkbashisms". I could patch all the #! headers and audit all the
calls to "sh" directly, but that seems a bit unmaintainable in the
long-run.
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
live well,
vagrant
Attachment:
signature.asc
Description: PGP signature