From: "Ludovic Courtès" <ludo@gnu.org>
To: "Wicki Gabriel (wicg)" <wicg@zhaw.ch>
Cc: "61732@debbugs.gnu.org" <61732@debbugs.gnu.org>
Subject: bug#61732: "Unbound variable: %build-inputs
Date: Mon, 27 Feb 2023 22:17:14 +0100 [thread overview]
Message-ID: <878rgihkpx.fsf_-_@gnu.org> (raw)
In-Reply-To: <ZR0P278MB02681231254E2A24B410623DC1AB9@ZR0P278MB0268.CHEP278.PROD.OUTLOOK.COM> (Wicki Gabriel's message of "Thu, 23 Feb 2023 12:56:43 +0000")
Hi Wicki,
"Wicki Gabriel (wicg)" <wicg@zhaw.ch> skribis:
> Sorry, that last email was sent a little too early.
>
>
> I tried said cross-compilation with this command: `guix build perl-gd --target=aarch64-linux-gnu` and could provoke the same error message also with perl-commonmark.
>
> It also happens with riscv64-linux-gnu and arm-linux-gnueabihf as target (i haven't tested all of them, though).
This issue was fixed (or rather sidestepped) a few days ago with this
commit:
d00c2e9c2b * services: console-font, kmscon: Refer to native 'font-gnu-unifont' builds.
Assuming you stumbled upon this error while cross-building a system
image with ‘guix system image --target=aarch64-linux-gnu’ or similar,
the problem is now solved.
If you really want to cross-build ‘perl-gd’, then we’re not there yet
but I think Maxim made some progress on this front.
HTH,
Ludo’.
prev parent reply other threads:[~2023-02-27 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 12:42 bug#61732: "Unbound variable: %build-inputs Wicki Gabriel (wicg)
2023-02-23 12:56 ` bug#61732: "Unbound variable: %build-inputs" in Cross-Compilation Context Wicki Gabriel (wicg)
2023-02-27 21:17 ` Ludovic Courtès [this message]
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=878rgihkpx.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=61732@debbugs.gnu.org \
--cc=wicg@zhaw.ch \
/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.