From: elaexuotee@wilsonb.com
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: help-guix@gnu.org
Subject: Re: Running shepherd as user: incompatible bytecode version
Date: Mon, 19 Apr 2021 01:49:49 +0900 [thread overview]
Message-ID: <3JYC5IRAZ6WMK.3RNTM1QLRJONL@wilsonb.com> (raw)
In-Reply-To: <e0a9437beddb127f4c9ee115c649bcfaac6cc694.camel@zaclys.net>
Léo Le Bouter <lle-bout@zaclys.net> wrote:
> I get the same issue, the shepherd package uses GNU Guile 3.0.2 and GNU
> Guix provides GNU Guile 3.0.5 under the 'guile' package specification
> name.
>
> I am not sure this is the cause, since shepherd is wrapped to use GNU
> Guile 3.0.2.
>
> I am also still looking for a solution.
>
> Léo
Thanks for the quick sanity check.
I spent a little time looking into this. The problem seems to be that Shepherd
is executed from Guile 3.0.2 while its %load-compiled-path contains compiled
modules for 3.0.5.
This ultimately stems from the fact that the `guix' package has
`guile-3.0-latest' on its inputs while while `shepherd' has just `guile-3.0'.
Ideally, we'd just update Shepherd to use the same Guile as guix, but
unfortunately, Shepherd (currently, 0.8.1) fails several of its tests if you
naively try replacing the input. I have also been hitting unrelated build
obstacles trying to test building against master.
Anyway, if we must stick with Guile 3.0.2, then maybe it makes sense to include
something like a guile-module-union (from guix/self.scm) and shove this into
the %load-path and $load-compiled-path of the /bin/shepherd script. I haven't
looked too deeply into doing this yet.
Finally, as a quick workaround, you can call shepherd with an empty
%load-compiled-path to supress the warnings:
$ GUILE_LOAD_COMPILED_PATH= shepherd
All the modules will still need to be run through the interpreter, though, so
startup time remains horrendously slow when using that fccache example.
next prev parent reply other threads:[~2021-04-18 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 15:39 Running shepherd as user: incompatible bytecode version elaexuotee
2021-04-15 22:19 ` Léo Le Bouter
2021-04-18 16:49 ` elaexuotee [this message]
2023-02-12 8:09 ` elaexuotee
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=3JYC5IRAZ6WMK.3RNTM1QLRJONL@wilsonb.com \
--to=elaexuotee@wilsonb.com \
--cc=help-guix@gnu.org \
--cc=lle-bout@zaclys.net \
/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.