Hi Zelphir, Zelphir Kaltstahl <zelphirkaltst...@posteo.de> writes:
> This definitely is helpful! Glad I could be of some help :). > I'm sorry for the delay in responding. Thank you for your efforts! No worries. > I hit other errors when leaving away the --pure and I have the suspicion, that > gnu-build-system requires me to have a configure script in the git tree of my > repository, which I did not know before I saw it failing with a 127 error on > calling a configure script, which is/was not commited in my repository. I will > probably have to revise a section somewhere in my guile-hall packaging guide, > to > note, that one should add the configure script, even though it is generated > by hall. Hmm, the bootstrap phase in gnu-build-system should invoke `autoreconf -vif` if the package contains either a `configure.ac` or `configure.in` and does not contain a `bootstrap`, `bootstrap.sh` or `autogen.sh`. At least that what I get from reading the source: gnu-build-system.scm:203 [0] [0] https://git.savannah.gnu.org/cgit/guix.git/tree/guix/build/gnu-build-system.scm I also ran it on one of my projects that are using guile-hall, which does not have a configure script and it build it just fine. Maybe you have one of those bootstrap scripts that does not generate a configure script? -- s/Fred[re]+i[ck]+/Fredrik/g
