unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
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: Sat, 3 Sep 2016 14:59:54 +0200	[thread overview]
Message-ID: <CAL1_imnCwWvFeeJK=FRJV5JACA4LnguEWMrAHZ9m8EqqHfrfhQ@mail.gmail.com> (raw)
In-Reply-To: <87oa45nnup.fsf@gnu.org>

> It’s on purpose, and packages rarely (if even) need to refer to
> #:native-inputs; only a couple of phases in gnu-build-system.scm refer
> to #:native-inputs.
>
> In which context do you need to refer to #:native-inputs?

Cross-compiling the linux kernel.

> ;; Apply the neat patch.
> (system* "patch" "-p1" "--force"
>                "-i" (assoc-ref inputs "patch/freedo+gnu"))

and

> (mit    (assoc-ref inputs "module-init-tools")))

fail for no "real" reason. I could add a (if target native-inputs
inputs) but it seems ugly and think it might be a common problem?

  reply	other threads:[~2016-09-03 13:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 21:26 Cross-building GuixSD (and maybe using pre-built toolchains) 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 [this message]
2016-09-03 21:18               ` Ludovic Courtès
2016-09-03 21:27                 ` David Craven
  -- strict thread matches above, loose matches on Subject: below --
2016-08-31 16:15 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
2016-09-01 11:16         ` Ludovic Courtès
2016-09-01 11:59       ` 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='CAL1_imnCwWvFeeJK=FRJV5JACA4LnguEWMrAHZ9m8EqqHfrfhQ@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).