From: Ryan Sundberg <ryan@arctype.co>
To: guix-devel@gnu.org
Subject: Re: How to solve "abiI-check: recompilation needed"
Date: Thu, 16 Sep 2021 08:46:58 -0700 [thread overview]
Message-ID: <e13c1e35-8f79-2427-2f7d-3ffb1f02f2b3@arctype.co> (raw)
In-Reply-To: <0796c4bf-c8e8-34a4-b7ce-5a537492c32b@crazy-compilers.com>
[-- Attachment #1.1: Type: text/plain, Size: 1196 bytes --]
I turn auto-compilation off with --no-auto-compile when developing guile
code, that helps. I don't think there's a perfect way around this issue
regarding stale caches without fixing up guile itself. Other than that
if you put your code for make-go (I don't know what this program is,
sorry) into a (package), it should compile correctly without any cache
issues for release builds.
+$0.02
--
Sincerely,
Ryan Sundberg
On 9/16/21 3:56 AM, Hartmut Goebel wrote:
> Hi,
>
> quite often, after "git pull" I'm facing this error when running
> "make-make-go":
>
> $ make make-go
> Compiling Scheme modules...
> Compiling Scheme modules...
> [ 69%] LOAD gnu/packages/admin.scm
> error: failed to load 'gnu/packages/check.scm':
> ice-9/eval.scm:293:34: In procedure abi-check: #<record-type <package>>:
> record ABI mismatch; recompilation needed
> make: *** [Makefile:7096: make-packages-go] Fehler 1
>
> How can I solve this, without removing and rebulding *all* files - which
> is time consuming and a waste of electric power.
>
> I already tried without success "rm gnu/package.go" as well as removing
> some other .go-files listed in the output.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2021-09-16 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 10:56 How to solve "abiI-check: recompilation needed" Hartmut Goebel
2021-09-16 14:23 ` Ricardo Wurmus
2021-09-17 20:03 ` Maxim Cournoyer
2021-09-18 13:13 ` Maxime Devos
2021-09-16 15:46 ` Ryan Sundberg [this message]
2021-09-16 16:47 ` Ricardo Wurmus
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=e13c1e35-8f79-2427-2f7d-3ffb1f02f2b3@arctype.co \
--to=ryan@arctype.co \
--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 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).