From: Ricardo Wurmus <rekado@elephly.net>
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: Fri, 13 Jul 2018 20:23:32 +0200 [thread overview]
Message-ID: <87efg7q9jv.fsf@elephly.net> (raw)
In-Reply-To: <87lgafgwei.fsf@gnu.org>
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
>> So what I was saying is probably: we have x86 NOW, can we use it and do
>> we want that somehow? OR do we plan some of the work above, and go that
>> route?
>
> I think we should try and use what we have now in ‘wip-bootstrap’, and
> keeps things unchanged for ARM and GNU/Hurd. Ricardo?
I agree. We need to make sure, though, that the Guix build
infrastructure doesn’t add more complicated packages to the environment
that are not needed.
>>>>> there's also another option you didn't mention: ditching the 2.0
>>>>> bootstrap Guile in favor of Mes. That can be done in several steps:
>>>>
>>>>> 1. Replace the guile-2.0.*.xz binary tarballs with Mes, and add a step
>>>>> that builds Guile 2.x using our big bootstrap GCC binary.
>>>> Slow but possible
>>
>> Yes, performance is really the thing here. Currently, mes is about 30x
>> slower than Guile. It will definately not work if mes has to interpret
>> all of gnu/packages/*.scm, it may work if we can do something smart.
>
> No no, in my view we’d use Mes simply as the guile-for-build in the
> early derivations (the interpreter that runs the build phases from (guix
> build build-system)).
>
> It’s a job where we don’t need much performance, but we need the POSIX
> layer—‘system*’, (ice-9 ftw), and so on.
Right. We would need to cut out Guile on the build side.
> What’s the exact status of ‘wip-bootstrap’ on non Intel arches? Is it
> still like ‘master’? If it is, that’s fine.
>
> Does it use the Mes/MesCC/tcc path for i686 only, or is it i686 +
> x86_64? (I would expect the latter.)
>
> If there are no regressions, I’d be willing to simply merge it in
> core-updates. I’d like some of us to take another look at it—Ricardo,
> Mark, and anyone with an interest in this. And then I guess we could
> go.
I would love to take a closer look again before merging it.
Unfortunately, these days I’m a bit short on time as I’m on “vacation”
with other plans imposed on my schedule.
--
Ricardo
next prev parent reply other threads:[~2018-07-13 18:39 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
2018-07-13 12:20 ` Ludovic Courtès
2018-07-13 14:19 ` Jan Nieuwenhuizen
2018-07-13 18:23 ` Ricardo Wurmus [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efg7q9jv.fsf@elephly.net \
--to=rekado@elephly.net \
--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 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.