From: Ricardo Wurmus <rekado@elephly.net>
To: bootstrappable@freelists.org
Cc: guix-devel@gnu.org
Subject: Re: [bootstrappable] Re: prototyping the full source bootstrap path
Date: Mon, 20 Nov 2017 12:42:20 +0100 [thread overview]
Message-ID: <87vai5w50j.fsf@elephly.net> (raw)
In-Reply-To: <87y3n15mru.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> So the next steps in the dependency graph are:
>
> mes-boot -> mescc -> tinycc -> gcc@4.7 -> gcc
>
> Do I get this right?
It’s not clear yet. An alternative approach is to try to build Guile
first by using mes as the bootstrap Scheme interpreter.
Also: I wonder if we can simplify these bootstrap packages in Guix, so
that they can be built with even fewer build-time features.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-11-21 19:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 22:31 prototyping the full source bootstrap path Jan Nieuwenhuizen
2017-11-20 9:20 ` [bootstrappable] " Ludovic Courtès
2017-11-20 11:42 ` Ricardo Wurmus [this message]
2017-11-20 18:41 ` [bootstrappable] " Jan Nieuwenhuizen
2017-11-20 18:48 ` Orians, Jeremiah (DTMB)
2017-11-20 21:55 ` Ludovic Courtès
2017-11-21 12:59 ` Orians, Jeremiah (DTMB)
2017-11-21 17:52 ` Jan Nieuwenhuizen
2017-11-21 18:23 ` Orians, Jeremiah (DTMB)
2017-11-23 4:56 ` Mark H Weaver
2017-11-27 12:42 ` Orians, Jeremiah (DTMB)
2017-11-23 17:55 ` Jan Nieuwenhuizen
2017-11-23 22:12 ` Ricardo Wurmus
2017-11-25 10:51 ` Jan Nieuwenhuizen
2017-11-20 18:48 ` Jan Nieuwenhuizen
2017-11-20 19:22 ` Gábor Boskovits
2017-11-20 12:45 ` [bootstrappable] " Orians, Jeremiah (DTMB)
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vai5w50j.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=bootstrappable@freelists.org \
--cc=guix-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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.