[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cross-building GuixSD (and maybe using pre-built toolchains)

From: Ludovic Courtès
Subject: Re: Cross-building GuixSD (and maybe using pre-built toolchains)
Date: Sat, 03 Sep 2016 23:18:05 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

David Craven <address@hidden> skribis:

>> 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"))

This looks like a remnant of the past; nowadays it would work to add
‘%boot-logo’ to ‘patches’ in ‘origin’.  We should do that.

> 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?

Hmm, I can see two occurrences of

  (assoc-ref (or native-inputs inputs) "bash")

in gnu/packages/*.scm.

Not ideal, but I’d suggest sticking to that for now.  :-)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]