From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Why do we not cross-compile bootstrap binaries?
Date: Thu, 07 Dec 2017 18:04:43 -0800 [thread overview]
Message-ID: <87d13qt1ok.fsf@gmail.com> (raw)
In-Reply-To: <87fu90vgsg.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 26 Nov 2017 23:03:43 +0100")
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> In practice, apart from x86_64-linux which was bootstrapped on NixOS, we
> always cross-compile to bootstrap new architectures:
>
> https://www.gnu.org/software/guix/manual/html_node/Porting.html
>
> That was the case for all the non-Intel arches and for GNU/Hurd.
>
> Is that what you meant?
My question was more about: why do we check in bootstrap binaries for
different architectures, instead of checking in bootstrap binaries for
one "base" architecture and then generating the bootstrap binaries for
other architectures from that "base" architecture. I think Efraim's
answer confirmed my understanding, which is that basically we want to
avoid treating any single platform as special.
Thank you for the reply!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-12-08 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 0:47 Why do we not cross-compile bootstrap binaries? Chris Marusich
2017-11-26 9:03 ` Efraim Flashner
2017-11-26 22:03 ` Ludovic Courtès
2017-12-08 2:04 ` Chris Marusich [this message]
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=87d13qt1ok.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--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).