From: Andy Wingo <wingo@igalia.com>
To: Michael Schierl <schierlm@gmx.de>
Cc: guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
guile-user@gnu.org, bootstrappable@freelists.org
Subject: Re: [bootstrappable] Re: Can Guile be bootstrapped from source without psyntax-pp.scm?
Date: Tue, 16 Mar 2021 09:59:30 +0100 [thread overview]
Message-ID: <87k0q7scct.fsf@igalia.com> (raw)
In-Reply-To: <6d533331-87f7-414b-7422-276530798194@gmx.de> (Michael Schierl's message of "Mon, 15 Mar 2021 20:50:07 +0100")
On Mon 15 Mar 2021 20:50, Michael Schierl <schierlm@gmx.de> writes:
> Am 15.03.2021 um 18:09 schrieb Ludovic Courtès:
>> Woow, this is great news! I think it would be great towards importing
>> it in Guile proper.
>>
>> To do that, I think we should first get Andy’s opinion on the approach.
>
> I don't think upstream is very interested in having psyntax-pp.scm
> bootstrappable.
Why do you say that? :)
> 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!
Andy
next prev parent reply other threads:[~2021-03-16 8:59 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 [this message]
2021-05-13 20:22 ` Michael Schierl
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=87k0q7scct.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=bootstrappable@freelists.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=schierlm@gmx.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).