From: Mathieu Lirzin <mthl@gnu.org>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Re-using bootstrap in the half-strap
Date: Mon, 24 Oct 2016 18:48:58 +0200 [thread overview]
Message-ID: <87vawhelqd.fsf@gnu.org> (raw)
In-Reply-To: <871sz52294.fsf@dustycloud.org> (Christopher Allan Webber's message of "Mon, 24 Oct 2016 10:30:31 -0500")
Hello,
Christopher Allan Webber <cwebber@dustycloud.org> writes:
> A thought this morning... one challenge with Guile's 2.1 branch is it
> takes a lonnnng time to bootstrap. There are good reasons for this, and
> Andy Wingo has documented them:
>
> http://wingolog.org/archives/2016/01/11/the-half-strap-self-hosting-and-guile
>
> However, I can't help but wonder if we could reuse the initial
> bootstrapped compiler. What if we had an external package that
> contained *just* the scheme interpreter used to bootstrap the rest of
> the system? We might not need to separate the codebase, but have this
> be a separate make output.
>
> If you could package *just* the bootstrapped compiler, if a user doesn't
> feel like waiting through the whole bootstrap process, they could use
> the existing bootstrap package, like:
>
> ./configure --with-bootstrap=/path/to/guile-bootstrap
>
> and maybe we could have a guile-bootstrap package in guix, etc. If you
> want to do the whole bootstrap yourself in the Guile package, you could
> do so, but it wouldn't be a requirement, assuming you had that separate
> package...
>
> Thoughts? Useful? Badly informed?
> - Chris
I feel the same way. I don't know about the technical details, but
such convenience would be more than welcome.
Thanks,
--
Mathieu Lirzin
next prev parent reply other threads:[~2016-10-24 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 15:30 Re-using bootstrap in the half-strap Christopher Allan Webber
2016-10-24 16:48 ` Mathieu Lirzin [this message]
2016-10-25 21:13 ` Ludovic Courtès
2016-10-26 22:30 ` Christopher Allan Webber
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=87vawhelqd.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=cwebber@dustycloud.org \
--cc=guile-devel@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).