From: Michael Schierl <schierlm@gmx.de>
To: bootstrappable@freelists.org, Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org, guile-user@gnu.org
Subject: Re: [bootstrappable] Re: Can Guile be bootstrapped from source without psyntax-pp.scm?
Date: Thu, 13 May 2021 22:22:44 +0200 [thread overview]
Message-ID: <7fe13f52-acf1-f32e-b44d-6e8bf11bdc23@gmx.de> (raw)
In-Reply-To: <87k0q7scct.fsf@igalia.com>
Hello all,
Am 16.03.2021 um 09:59 schrieb Andy Wingo:
> On Mon 15 Mar 2021 20:50, Michael Schierl <schierlm@gmx.de> writes:
>> In Guile 3.0.3 they broke even the `make ice-9/psyntax-pp.scm.gen`
>> target, and did not repair it even in Guile 3.0.5, that's why I used
>> 3.0.2 for the bootstrap.
>
> Strange -- I used it many times over the past couple months without
> problems. But I see now from your patches what the issue was -- and omg
> how embarrassing, I must have a stale canonicalize.go file hanging
> around in the tree. Goes to show how important bootstrapping is!
Yes. Stale files required for building are an even bigger problem than
non-source artifacts in the source code required for building...
As the psyntax-pp.scm.gen target was fixed in 3.0.7, I updated my
bootstrap (the changes where fairly minor):
https://github.com/schierlm/guile-psyntax-bootstrapping/commit/e2f2b1d5271ff8fddb22706863bb0d719e844dd5
I also pushed two tags (guile-3.0.2 and guile 3.0.7) to the repo so that
users can have stable links for bootstrapping a particular Guile version
without having to fetch a particular commit id.
Regards,
Michael
next prev parent reply other threads:[~2021-05-13 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 22:42 Can Guile be bootstrapped from source without psyntax-pp.scm? Michael Schierl
2021-03-14 13:57 ` [bootstrappable] " Jan Nieuwenhuizen
2021-03-14 14:18 ` Michael Schierl
2021-03-15 17:09 ` Ludovic Courtès
2021-03-15 19:50 ` Michael Schierl
2021-03-16 8:59 ` Andy Wingo
2021-05-13 20:22 ` Michael Schierl [this message]
2021-03-17 17:25 ` Ludovic Courtès
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=7fe13f52-acf1-f32e-b44d-6e8bf11bdc23@gmx.de \
--to=schierlm@gmx.de \
--cc=bootstrappable@freelists.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=wingo@igalia.com \
/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).