all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josselin Poiret <dev@jpoiret.xyz>
To: Leo Famulari <leo@famulari.name>
Cc: Andreas Enge <andreas@enge.fr>,
	guix-devel@gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764
Date: Fri, 31 Mar 2023 10:15:06 +0200	[thread overview]
Message-ID: <87a5zts5f9.fsf@jpoiret.xyz> (raw)
In-Reply-To: <ZCYY/JVIeizo1BtV@jasmine.lan>

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

Hi Leo and Andreas,

Leo Famulari <leo@famulari.name> writes:

> On Thu, Mar 30, 2023 at 08:49:43PM +0200, Josselin Poiret wrote:
>> 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`.
>
> I saw this error too, but it went away after `make clean-go && make`.

Don't want to praise myself too much, but the above command should only
delete .go files which contain references to perl-extutils-pkgconfig,
thus avoiding a rebuild of all go files!

Best,
-- 
Josselin Poiret

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

  reply	other threads:[~2023-03-31  8:15 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a5zts5f9.fsf@jpoiret.xyz \
    --to=dev@jpoiret.xyz \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --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 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.