John Darrington skribis:
> On Wed, Nov 19, 2014 at 09:53:24AM +0100, Ludovic Court??s wrote:
[...]
> 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
On Wed, Nov 19, 2014 at 09:53:24AM +0100, Ludovic Court??s wrote:
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.)
OK, I will try that
John Darrington skribis:
> On Tue, Nov 18, 2014 at 09:36:10PM +0100, Ludovic Court??s wrote:
> John Darrington skribis:
>
> > From: John Darrington
> >
> > * gnu/packages/glib.scm (glib) : Moved inputs to native-inputs,
> > and change "inputs" to "%build-inputs"
On Tue, Nov 18, 2014 at 09:36:10PM +0100, Ludovic Court??s wrote:
John Darrington skribis:
> From: John Darrington
>
> * gnu/packages/glib.scm (glib) : Moved inputs to native-inputs,
> and change "inputs" to "%build-inputs"
OK for the former, but why th
John Darrington skribis:
> From: John Darrington
>
> * 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.
Also, what abo
From: John Darrington
* gnu/packages/glib.scm (glib) : Moved inputs to native-inputs,
and change "inputs" to "%build-inputs"
---
gnu/packages/glib.scm | 47 ---
1 file changed, 28 insertions(+), 19 deletions(-)
diff --git a/gnu/packages/glib.scm b
