Re: [PATCH] gnu: fix some issues cross-compiling glib

[ludo@gnu.org (Ludovic Courtès)]

John Darrington <john@darrington.wattle.id.au> skribis:

> On Tue, Nov 18, 2014 at 09:36:10PM +0100, Ludovic Court??s wrote:
>      John Darrington <jmd@gnu.org> skribis:
>      
>      > From: John Darrington <john@darrington.wattle.id.au>
>      >
>      > * gnu/packages/glib.scm (glib) : Moved inputs to native-inputs,
>      >   and change "inputs" to "%build-inputs"
>      
>      OK for the former, but why the latter?  In general I think it???s
>      stylistically better to refer to the ???inputs??? argument.
>
> I don't know why,  but it fails to build with "inputs".  (assoc-ref "inputs" "bash")
> returns #f  

You probably need (assoc-ref (or native-inputs inputs) "bash"), meaning
you’ll refer to the native Bash both when compiling natively and when
cross-compiling (as done in ATLAS and OpenSSL.)

>      Also, what about somehow grouping big-rebuild changes together?  I???m
>      slightly worried by the post-release chaos that might occur.  :-)
>      Maybe core-updates, or maybe a more specific branch for
>      cross-compilation fixes?
>
> I can push it to core-updates if you like.  How big is big?  

core-updates no longer exists.  Perhaps let’s just make a
‘cross-compilation’ branch (or ‘arm’?) with all such changes.
Then we’ll arrange for Hydra to build that branch, and merge it once
it’s stable and mostly built.

WDYT?

Thanks,
Ludo’.