From: Fredrik Salomonsson <plattfot@posteo.net>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
help-guix <help-guix@gnu.org>
Subject: Re: Setting up guix source tree for testing a package
Date: Wed, 17 Mar 2021 17:22:07 -0700 [thread overview]
Message-ID: <87pmzxs440.fsf@posteo.net> (raw)
In-Reply-To: <f20ee682-e825-f3ed-58d6-6cff7c0b408c@posteo.de>
Hi Zelphir,
Zelphir Kaltstahl <zelphirkaltstahl@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
next prev parent reply other threads:[~2021-03-18 0:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 23:31 Setting up guix source tree for testing a package Zelphir Kaltstahl
2021-03-12 1:01 ` Fredrik Salomonsson
2021-03-17 20:46 ` Zelphir Kaltstahl
2021-03-18 0:22 ` Fredrik Salomonsson [this message]
2021-03-12 19:59 ` Joshua Branson
2021-03-17 20:49 ` Zelphir Kaltstahl
2021-03-12 21:52 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmzxs440.fsf@posteo.net \
--to=plattfot@posteo.net \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).