unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: Paul Alesius <paul@unnservice.com>, 65523-done@debbugs.gnu.org
Subject: bug#65523: package `guile@3.0.9' has an invalid input: ("_" #<syntax-transformer pkg-config>)
Date: Thu, 01 Feb 2024 23:57:18 -0500	[thread overview]
Message-ID: <87r0hvo441.fsf@gmail.com> (raw)
In-Reply-To: <87h6odkobm.fsf@jpoiret.xyz> (Josselin Poiret's message of "Sat,  02 Sep 2023 09:48:45 +0200")

Hi,

Josselin Poiret <dev@jpoiret.xyz> writes:

> 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`.

Thanks for the answer, Josselin!

Closing.

-- 
Maxim




      reply	other threads:[~2024-02-02  4:58 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
2024-02-02  4:57   ` Maxim Cournoyer [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

  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=87r0hvo441.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=65523-done@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 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).