From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: "Timothy Sample" <samplet@ngyro.com>,
"Ludovic Courtès" <ludo@gnu.org>,
"Nicolas Goaziou" <mail@nicolasgoaziou.fr>,
39655@debbugs.gnu.org
Subject: [bug#39655] [PATCH core-updates] doc: Add 'Scheme-only Bootstrap' node.
Date: Mon, 18 May 2020 09:37:45 +0200 [thread overview]
Message-ID: <87h7wdofqu.fsf@gnu.org> (raw)
In-Reply-To: <20200518065745.GD18220@E5400> (Efraim Flashner's message of "Mon, 18 May 2020 09:57:45 +0300")
Efraim Flashner writes:
> I have to ask since we're talking about bootstrapability; is it actually
> not bootstrappable or is it just harder/more complex? (The question is
> more about the wording than about the logistics of it.)
gzip is about 7000 LOC of simple C, can be compiled with tinycc (and
probably mescc), and we have gzip in Gash. That Scheme code is not
trivial but with not too much work we can have Mes run that code. It's
also conceivable to have an M2-Planet port of gzip.
xz is about 25,000 LOC of C and I only managed to build it after having
a full fledged gcc-4.6, gcc-2.95 or tinycc did not work for me.
So, if SED only ships xz-compressed tarballs, that makes
creating/maintaining the GNU bootstrap story more difficult.
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:[~2020-05-18 7:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 12:44 [bug#39655] [PATCH core-updates] doc: Add 'Scheme-only Bootstrap' node Jan Nieuwenhuizen
2020-02-19 15:58 ` Ludovic Courtès
2020-05-17 12:43 ` Jan Nieuwenhuizen
2020-05-17 12:51 ` Jan Nieuwenhuizen
2020-05-17 22:05 ` Nicolas Goaziou
2020-05-18 5:27 ` Jan Nieuwenhuizen
2020-05-18 6:57 ` Efraim Flashner
2020-05-18 7:37 ` Jan Nieuwenhuizen [this message]
2020-05-18 7:37 ` Nicolas Goaziou
2020-05-18 7:50 ` Jan Nieuwenhuizen
2020-05-18 17:53 ` Timothy Sample
2020-05-22 14:20 ` bug#39655: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7wdofqu.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=39655@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=ludo@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=samplet@ngyro.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.
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.