From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Brian Kubisiak <brian@kubisiak.com>, 54618@debbugs.gnu.org
Subject: [bug#54618] [PATCH] gnu: lbzip2: Fix cross-compilation.
Date: Tue, 29 Mar 2022 08:07:51 +0200 [thread overview]
Message-ID: <b91791f5caf8be939d7e41a1dc9bbaec52d1fdce.camel@ist.tugraz.at> (raw)
In-Reply-To: <20220329013641.gfixewbrmu2qkz34@peregrine>
Am Montag, dem 28.03.2022 um 18:36 -0700 schrieb Brian Kubisiak:
> * gnu/packages/compression.scm (lbzip2)[arguments]: Add (or
> native-inputs inputs) to ASSOC-REF.
> ---
> gnu/packages/compression.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/compression.scm
> b/gnu/packages/compression.scm
> index 3edaecd951..34e9fa49de 100644
> --- a/gnu/packages/compression.scm
> +++ b/gnu/packages/compression.scm
> @@ -411,8 +411,8 @@ (define-public lbzip2
> `(#:phases
> (modify-phases %standard-phases
> (add-after 'unpack 'unpack-gnulib
> - (lambda* (#:key inputs #:allow-other-keys)
> - (let ((gnulib (assoc-ref inputs "gnulib")))
> + (lambda* (#:key inputs native-inputs #:allow-other-
> keys)
> + (let ((gnulib (assoc-ref (or native-inputs inputs)
> "gnulib")))
> (copy-recursively gnulib "lib")
> (setenv "PATH" (string-append "lib:" (getenv
> "PATH")))
> #t)))
Note that referring to inputs by name is discouraged. In this case, the
gnulib origin should be inlined (see ppsspp or gnome-recipes for
examples on how that is done). I don't think there is a native vs.
non-native distinction for origins, but if there is, simply use #+
instead of #$.
Cheers
next prev parent reply other threads:[~2022-03-29 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 1:36 [bug#54618] [PATCH] gnu: lbzip2: Fix cross-compilation Brian Kubisiak
2022-03-29 6:07 ` Liliana Marie Prikler [this message]
2022-03-29 9:05 ` Maxime Devos
2022-03-30 1:45 ` [bug#54618] [PATCH v2] " Brian Kubisiak
2022-03-30 10:39 ` bug#54618: [PATCH] " Mathieu Othacehe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b91791f5caf8be939d7e41a1dc9bbaec52d1fdce.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=54618@debbugs.gnu.org \
--cc=brian@kubisiak.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.