Ludovic Courtès <[email protected]> writes: > Andreas Enge <[email protected]> skribis: > >> Am Wed, Mar 25, 2026 at 12:17:57PM +0100 schrieb Tomas Volf: >>> ;;; WARNING: loading compiled file >>> /run/current-system/profile/lib/guile/3.0/site-ccache/guix/utils.go failed: >>> ;;; In procedure load-thunk-from-memory: incompatible bytecode version >>> ;;; compiling >>> /run/current-system/profile/share/guile/site/3.0/guix/utils.scm >>> >>> I did not see anything in pull news about guile-3.0 being deprecated, >>> there is no warning printed, and it is still used for building guile >>> libraries, so I assume this is a bug. >> >> notice that guile-3.0 is now version 3.0.11, > > More precisely, ‘guile-3.0-latest’ (used by Guix) is 3.0.11, but > ‘guile-3.0’ is unchanged—see commit > c3fefb065c53703e3dc6507c813182101c5c3a38. > > Most likely what happens is that you’re running 3.0.9 but those Guix > modules were built by 3.0.11.
Well, yes, I am installing guile-3.0 into my home environment, so my Guile is 3.0.9, however I am not sure how if I should change that. Most (all?) guile- packages are still compiled against 3.0.9. Based on the fact that I am getting an error, 3.0.9 and 3.0.11 do not seem compatible enough (if they were, I would not be getting the error and there would be no need for the guile-3.0 and guile-3.0-latest split I guess). Turns out part of the problem was my .guile file (I had no idea that (when #f (@ (foo) bar)) loads the (foo) module). But even without that, I am unsure how to use Guix modules and Guile packages together, since one is using (and tested with) .11 and other others are using (and tested with) .9. I am probably just missing something. :) Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
