From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Jeremiah@pdp10.guru
Subject: Re: Preparing the reduced bootstrap tarballs
Date: Sun, 18 Nov 2018 19:39:37 +0100 [thread overview]
Message-ID: <87ftvys00m.fsf@gnu.org> (raw)
In-Reply-To: <8736ryutoy.fsf@netris.org> (Mark H. Weaver's message of "Sun, 18 Nov 2018 13:27:30 -0500")
Mark H Weaver writes:
> Anyway, I've answered my own question by looking at:
>
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/make-bootstrap.scm?h=core-updates-next&id=d9ed0a46301e259c3082fcc67678e72ceae19a2d#n778
>
> which indicates to me that although gcc, binutils, and glibc have been
> eliminated from the Guix bootstrap binaries, they still include
> statically-linked versions of Guile, Coreutils, Bzip2, XZ, Gawk, Tar,
> and Grep. These are the remaining precompiled binaries that I'm worried
> about.
As far as I'm concerned our next step after the Reduced Binary Seed
bootstrap--that is yet to be released from core-updates-next---is the
Scheme-only bootstrap.
The plan is to have Guile and Gash initially replace all coreutils&co
and build them from source early in the bootstrap phase, right after
having built tcc and GNU make. We have managed to build GNU make
without any dependency on any of the tool you mention (except for
Guile).
We're not there yet, gash cannot build mes or tcc. Also, the latest mes
0.18 release cannot support buillding bash yet. Lots of fun hacking
todo!
A next step could be to replace bootstrap-guile with mes, or create a
real small version of bootstrappable Guile.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2018-11-18 18:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 12:56 Preparing the reduced bootstrap tarballs Jeremiah
2018-11-18 18:27 ` Mark H Weaver
2018-11-18 18:39 ` Jan Nieuwenhuizen [this message]
2018-11-20 15:45 ` Timothy Sample
2018-11-21 20:32 ` Jan Nieuwenhuizen
2018-11-26 18:49 ` Timothy Sample
-- strict thread matches above, loose matches on Subject: below --
2018-11-21 3:36 Jeremiah
2018-11-20 0:26 jeremiah
2018-11-20 8:28 ` Ricardo Wurmus
2018-11-17 14:27 Jeremiah
2018-11-17 23:14 ` Mark H Weaver
2018-11-19 18:54 ` Giovanni Biscuolo
2018-11-15 20:39 Jeremiah
2018-11-16 18:27 ` Ludovic Courtès
2018-11-16 20:44 ` Jan Nieuwenhuizen
2018-11-17 14:05 ` Ludovic Courtès
2018-11-18 7:32 ` Jan Nieuwenhuizen
2018-11-18 10:02 ` Jan Nieuwenhuizen
2018-11-17 3:49 ` Mark H Weaver
[not found] <20181014085857.3863-1-janneke@gnu.org>
[not found] ` <20181014085857.3863-3-janneke@gnu.org>
[not found] ` <87r2gld3nt.fsf@gnu.org>
[not found] ` <875zxxax4f.fsf@gnu.org>
[not found] ` <87sh0z6m83.fsf@gnu.org>
[not found] ` <87ftwz9e9y.fsf@gnu.org>
[not found] ` <874ldccr9f.fsf@gnu.org>
2018-11-15 9:06 ` Ludovic Courtès
2018-11-15 15:44 ` Jan Nieuwenhuizen
2018-11-16 18:22 ` Ludovic Courtès
2018-11-16 20:52 ` Jan Nieuwenhuizen
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftvys00m.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=Jeremiah@pdp10.guru \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).