From: ludo@gnu.org (Ludovic Courtès)
To: David Craven <david@craven.ch>
Cc: help-guix@gnu.org
Subject: Re: Cross-building GuixSD (and maybe using pre-built toolchains)
Date: Wed, 31 Aug 2016 22:08:12 +0200 [thread overview]
Message-ID: <87d1kon1lf.fsf@gnu.org> (raw)
In-Reply-To: <CAL1_imnUdibN8604Jv9cVfKmg5uyym5FK4tNnPJAZDb1bMzpPA@mail.gmail.com> (David Craven's message of "Wed, 31 Aug 2016 18:15:40 +0200")
Hi David,
David Craven <david@craven.ch> skribis:
> So one issue that happens when cross building is for things that have
> the #:no-substitutes #t enabled. This is mainly found in service
> derivations for generating configuration files.
I think there’s currently no easy way to cross build a full GuixSD
anyway, like ‘guix system build --target=mips64el-linux-gnu’ (the
--target flag doesn’t exist yet). Or did you experiment in this area?
I’d be curious. It’s designed to allow this (in particular because
gexps are cross-compilation-aware), but I’ve never tried.
Ludo’.
next prev parent reply other threads:[~2016-08-31 20:08 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 [this message]
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
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=87d1kon1lf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=david@craven.ch \
--cc=help-guix@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).