From: David Craven <david@craven.ch>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Cross-building GuixSD (and maybe using pre-built toolchains)
Date: Thu, 1 Sep 2016 12:11:20 +0200 [thread overview]
Message-ID: <CAL1_imkfySB_c-USi+aSz2H3N8j-QxHvGVEom7CZTfzS-WSzkw@mail.gmail.com> (raw)
In-Reply-To: <87k2ewuj9e.fsf@gnu.org>
> Now, in most cases, the tiny Guile derivations created via
> ‘gexp->derivation’ et al. in GuixSD (e.g., the derivation that builds
> the initrd) could use, say, an x86_64 Guile, even if building for
> mips64el. However, it would be difficult to take advantage of this
> AFAICS.
So maybe I am taking the wrong approach. If an hypothetical --target
flag would exist, could it use natively built substitutes?
next prev parent reply other threads:[~2016-09-01 10:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 16:15 Cross-building GuixSD (and maybe using pre-built toolchains) David Craven
2016-08-31 20:08 ` Ludovic Courtès
2016-08-31 22:01 ` David Craven
2016-08-31 22:13 ` David Craven
2016-09-01 8:17 ` Ludovic Courtès
2016-09-01 10:11 ` David Craven [this message]
2016-09-01 11:16 ` Ludovic Courtès
2016-09-01 11:59 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2016-08-30 21:26 Paul Boddie
2016-08-31 20:04 ` Ludovic Courtès
2016-08-31 21:49 ` Paul Boddie
2016-09-01 8:10 ` Ludovic Courtès
2016-09-01 15:51 ` Paul Boddie
2016-09-01 19:43 ` Ludovic Courtès
2016-09-02 18:52 ` David Craven
2016-09-03 12:56 ` Ludovic Courtès
2016-09-03 12:59 ` David Craven
2016-09-03 21:18 ` Ludovic Courtès
2016-09-03 21:27 ` David Craven
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=CAL1_imkfySB_c-USi+aSz2H3N8j-QxHvGVEom7CZTfzS-WSzkw@mail.gmail.com \
--to=david@craven.ch \
--cc=help-guix@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.
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).