From: Josselin Poiret <dev@jpoiret.xyz>
To: Andreas Enge <andreas@enge.fr>, guix-devel@gnu.org
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764
Date: Thu, 30 Mar 2023 20:49:43 +0200 [thread overview]
Message-ID: <87lejers54.fsf@jpoiret.xyz> (raw)
In-Reply-To: <ZCVpwbih405gCSs4@jurong>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
Hi Andreas,
Andreas Enge <andreas@enge.fr> writes:
> Hello,
>
> it looks as if commit ff5f34ae757d709987896d6164bf125319a0f764 breaks
> building of at least one package, perl-gd, depending on
> perl-extutils-pkgconfig.
>
> The latter is now defined as
> (define-syntax perl-extutils-pkgconfig
> (identifier-syntax (perl-extutils-pkgconfig-for-target
> (%current-target-system))))
> which apparently does not play well with what is written in the former as
> (native-inputs
> (list perl-extutils-pkgconfig)) :
> guix package: error: gnu/packages/gd.scm:103:2: package `perl-gd@2.73' has an invalid input: ("_" #<syntax-transformer perl-extutils-pkgconfig>)
Usually errors which involve #<syntax-transformer> somewhere are caused
by stale .go files (guile doesn't know how to recompile dependent .scm
files). I would suggest a good old `grep -Rl --include '*.go'
perl-extutils-pkgconfig ./gnu | xargs rm`.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-03-30 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:51 Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764 Andreas Enge
2023-03-30 18:49 ` Josselin Poiret [this message]
2023-03-30 23:19 ` Leo Famulari
2023-03-31 8:15 ` Josselin Poiret
2023-04-01 16:13 ` Leo Famulari
2023-03-31 2:12 ` Maxim Cournoyer
2023-03-31 8:13 ` Josselin Poiret
2023-03-31 8:42 ` Andreas Enge
2023-03-31 14:02 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lejers54.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).