From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Cross-building GuixSD (and maybe using pre-built toolchains) Date: Sat, 03 Sep 2016 14:56:30 +0200 Message-ID: <87oa45nnup.fsf@gnu.org> References: <201608302326.38349.paul@boddie.org.uk> <201608312349.49957.paul@boddie.org.uk> <87shtkujko.fsf@gnu.org> <201609011751.42108.paul@boddie.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51390) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgAUv-0006m8-FD for help-guix@gnu.org; Sat, 03 Sep 2016 08:56:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bgAUr-0003GN-91 for help-guix@gnu.org; Sat, 03 Sep 2016 08:56:36 -0400 In-Reply-To: (David Craven's message of "Fri, 2 Sep 2016 20:52:51 +0200") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: David Craven Cc: help-guix@gnu.org Hi, David Craven skribis: > When adding cross-compilation support to the linux-libre package I > noticed that native-inputs are in #:key native-inputs when > cross-compiling but not when compiling natively. I think this is a > problem because we can't just use #:key native-inputs instead of #:key > inputs when adding support for cross-compilation. > > WDYT? It=E2=80=99s 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? Ludo=E2=80=99.