From: Lars-Dominik Braun <lars@6xq.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 57861@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>
Subject: [bug#57861] [PATCH] gnu: Add ultrastar-deluxe.
Date: Tue, 18 Oct 2022 09:56:22 +0200 [thread overview]
Message-ID: <Y05cJkuQCNiMlToz@noor.fritz.box> (raw)
In-Reply-To: <87k04yhmq3.fsf_-_@gnu.org>
Hi Ludo and Maxim,
> I think this is unnecessary: you can just #:use-module (gnu packages
> pascal) and have ‘fpc’ in ‘native-inputs’. Everything will be fine
> because ‘inputs’ is a thunked field (IOW, its evaluation is delayed).
the problem is that `make` fails with an error in that case. For me it’s
ice-9/eval.scm:293:34: error: gash: unbound variable
hint: Did you forget a `use-modules' form?
but YMMV. With #:autoload `make` succeeds, but throws similar
errors/warnings(?) in the process:
;;; Failed to autoload fpc in (gnu packages pascal):
;;; Throw to key `unbound-variable' with args `("resolve-interface" "no binding `~A' in module ~A" (fpc (gnu packages pascal)) #f)'.
That’s why I went for the route implemented in the initial patch. What
do we do now?
Lars
next prev parent reply other threads:[~2022-10-18 7:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 13:37 [bug#57861] [PATCH] gnu: Add ultrastar-deluxe Lars-Dominik Braun
2022-09-18 9:39 ` Maxime Devos
2022-09-21 11:52 ` [bug#57861] [PATCH v2] " Lars-Dominik Braun
2022-10-17 8:33 ` [bug#57861] [PATCH] " Ludovic Courtès
2022-10-17 13:25 ` Maxime Devos
2022-10-17 13:28 ` ( via Guix-patches via
2022-10-17 13:37 ` Maxime Devos
2022-10-17 16:44 ` Ludovic Courtès
2022-10-17 17:26 ` Maxime Devos
2022-10-17 8:35 ` Ludovic Courtès
2022-10-18 7:56 ` Lars-Dominik Braun [this message]
2022-10-18 12:44 ` Maxime Devos
2022-10-19 11:09 ` [bug#57861] [PATCH v2] " Lars-Dominik Braun
2022-11-07 22:59 ` bug#57861: [PATCH] " Ludovic Courtès
2022-10-18 12:49 ` [bug#57861] " Maxime Devos
2022-09-18 12:26 ` Maxime Devos
2022-11-07 21:41 ` Jonathan Brielmaier
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=Y05cJkuQCNiMlToz@noor.fritz.box \
--to=lars@6xq.net \
--cc=57861@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
/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.