From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"Orians, Jeremiah (DTMB)" <OriansJ@michigan.gov>
Subject: Re: bootstrap integration strategies
Date: Thu, 12 Jul 2018 21:52:01 +0200 [thread overview]
Message-ID: <87a7qww7tq.fsf@gnu.org> (raw)
In-Reply-To: <87a7qwjqsp.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Thu, 12 Jul 2018 19:40:38 +0200")
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
Jan Nieuwenhuizen writes:
> My idea was to remove gcc, glibc and binutils from the x86 bootstrap
> binaries (possibly one at a time) and replace them by M1+Mes+Tcc-built
> ones. Possibly by adding an alternative %bootstrap-binaries package
> without them. Then build the x86 system on top of that. Then, or
> meanwhile, start thinking about x86_64 or AArch64.
I've been trying to cleanup the dependencies in wip-bootstrap. I found
that using `package-with-bootstrap-guile' confuses guix graph. Or so it
seems, many duplicates of those packages show up.
Here's an image created with this hack: replace
`package-with-bootstrap-guile' with `identity' in commencement.scm and
mes.scm
Where it says `bootstrap-binaries0', not that binutils, gcc, glibc are
not used.
[-- Attachment #2: gcc-mesboot.png --]
[-- Type: image/png, Size: 847666 bytes --]
[-- Attachment #3: Type: text/plain, Size: 175 bytes --]
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-07-12 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 12:16 bootstrap integration strategies Orians, Jeremiah (DTMB)
2018-07-12 16:15 ` Ludovic Courtès
2018-07-12 17:10 ` Orians, Jeremiah (DTMB)
2018-07-12 17:40 ` Jan Nieuwenhuizen
2018-07-12 19:52 ` Jan Nieuwenhuizen [this message]
2018-07-13 12:20 ` Ludovic Courtès
2018-07-13 14:19 ` Jan Nieuwenhuizen
2018-07-13 18:23 ` Ricardo Wurmus
2018-07-16 11:11 ` Orians, Jeremiah (DTMB)
2018-07-16 21:37 ` Brett Gilio
2018-07-12 17:44 ` Jan Nieuwenhuizen
-- strict thread matches above, loose matches on Subject: below --
2018-07-09 20:55 Jan Nieuwenhuizen
2018-07-11 13:13 ` 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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7qww7tq.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=OriansJ@michigan.gov \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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).