From: Frank Terbeck <ft@bewatermyfriend.org>
To: guile-user <guile-user@gnu.org>
Subject: Re: build git version of Guile
Date: Tue, 02 Nov 2021 01:11:47 +0100 [thread overview]
Message-ID: <87ilxbh0vw.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <CACgrOxL1r0kkWgWZn9N_ytQ72bEeb2+bLrFM8nChgtqbp+POWA@mail.gmail.com> (Tim Meehan's message of "Mon, 1 Nov 2021 19:57:06 -0400")
Tim Meehan wrote:
> So ... building the git version of Guile seems different, I looked around
> for an INSTALLING file, and it isn't there (and neither is 'configure') ...
> any hints?
The ‘configure’ script itself can be generated. Many projects have
bootstrap or autogen scripts to do that.
Indeed guile uses ‘autogen.sh’.
Guile's documentation contains the procedure in HACKING.
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2021-11-02 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 23:57 build git version of Guile Tim Meehan
2021-11-02 0:11 ` Frank Terbeck [this message]
2021-11-05 0:40 ` Aleix Conchillo Flaqué
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilxbh0vw.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=guile-user@gnu.org \
/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).