From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764
Date: Thu, 30 Mar 2023 22:12:08 -0400 [thread overview]
Message-ID: <87wn2xy8hz.fsf@gmail.com> (raw)
In-Reply-To: <ZCVpwbih405gCSs4@jurong> (Andreas Enge's message of "Thu, 30 Mar 2023 12:51:45 +0200")
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>)
>
> I do not quite see where the problem lies, given that the same thing
> has been working for pkg-config for quite a while now...
> I noticed it on core-updates, but the commit comes from master.
I've seen this too, but it disappears if you byte-compile the project.
I'm not sure what that means, although it does seems sub-optimal that we
rely on byte-compilation for the code to evaluate correctly.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-03-31 2:12 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn2xy8hz.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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.