all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Paul Alesius <paul@unnservice.com>, 65523@debbugs.gnu.org
Subject: bug#65523: package `guile@3.0.9' has an invalid input: ("_" #<syntax-transformer pkg-config>)
Date: Sat, 02 Sep 2023 09:48:45 +0200	[thread overview]
Message-ID: <87h6odkobm.fsf@jpoiret.xyz> (raw)
In-Reply-To: <CAL8jUGVkBhNxxa6LUpz5HRfGvPV3O7-GfsmQFN_cF5sV2XHJMw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 922 bytes --]

Hi Paul,

Paul Alesius <paul@unnservice.com> writes:

> In the source code directory of Guix, when trying to build a package from
> gnu/packages/python-xyz.scm, it fails with the following error:
>
> guix build: error:
> /storage/src/guix/guix-gnu/guix/build-system/gnu.scm:146:8: package
> `guile@3.0.9' has an invalid input: ("_" #<syntax-transformer pkg-config>)

Usually, if you see `#<syntax-transformer ...>` anywhere in an error,
that means that something that used to be just a variable was turned
into a macro, but the other modules using it weren't recompiled
(reminder that macro expansion happens at compilation time).  This
happens because Guile doesn't have any dependency tracking!  You can
work around this by recompiling all files containing a reference to
pkg-config, I usually do `grep -Rl pkg-config --include '*.go' . | xargs
rm`, followed by `make`.

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

  reply	other threads:[~2023-09-02  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  7:19 bug#65523: package `guile@3.0.9' has an invalid input: ("_" #<syntax-transformer pkg-config>) Paul Alesius
2023-09-02  7:48 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2024-02-02  4:57   ` 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=87h6odkobm.fsf@jpoiret.xyz \
    --to=bug-guix@gnu.org \
    --cc=65523@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=paul@unnservice.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.