From: Efraim Flashner <efraim@flashner.co.il>
To: Andreas Enge <andreas@enge.fr>
Cc: Mathieu Othacehe <othacehe@gnu.org>, help-guix@gnu.org
Subject: Re: guix system disk-image failure aarch64 -> armhf
Date: Mon, 14 Sep 2020 16:24:19 +0300 [thread overview]
Message-ID: <20200914132419.GA17272@E5400> (raw)
In-Reply-To: <20200914093242.GA2756@jurong>
[-- Attachment #1: Type: text/plain, Size: 2440 bytes --]
On Mon, Sep 14, 2020 at 11:32:42AM +0200, Andreas Enge wrote:
> Hello Mathieu,
>
> thanks for your helpful reply!
>
> On Wed, Sep 09, 2020 at 11:11:18AM +0200, Mathieu Othacehe wrote:
> > That does not really explain the error though, but that's another
> > issue. The pending patch here[1], will hopefully help users specify
> > their target image. It means that you should be able to write:
> >
> > --8<---------------cut here---------------start------------->8---
> > guix system disk-image -t novena config.scm
> > --8<---------------cut here---------------end--------------->8---
>
> That looks really interesting, but I cannot meaningfully comment on the
> bug report. Maybe it is time after the summer vacation season to poke
> people more competent on the subject to comment :)
>
> > Until then, running something like:
> > --8<---------------cut here---------------start------------->8---
> > (run-with-store (open-connection)
> > (mlet* %store-monad
> > ((drv (lower-object (system-image my-image "armhf-linux")))
> > (build (built-derivations (list drv))))
> > (return #t)))
> > --8<---------------cut here---------------end--------------->8---
>
> If by running you mean calling "guile the-above-file.scm", then I get
> strange results. I just did a "guix system reconfigure"; "which guile"
> returns "/run/current-system/profile/bin/guile". However then I get lots
> of suspicious messages of this kind:
> ;;; In procedure load-thunk-from-memory: incompatible bytecode version
> ;;; WARNING: compilation of /run/current-system/profile/share/guile/site/3.0/guix/diagnostics.scm failed:
> ;;; Unbound variable: trivial-format-string?
>
> How can byte codes be incompatible if on one hand they are part of the
> profile, on the other hand I am running guile from the same profile?
>
> Andreas
>
I'm not sure about the trivial-format-string? warning (we should
probably investigate that). Guix is built with guile 3.0.2 and we have
guile-3.0.4. There was an unfortunate soversion bump with guile-3.0.2
and we've been having the incompatible bytecode version since with guile
programs. I've noticed it when launching shepherd as my user.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-14 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 8:04 guix system disk-image failure aarch64 -> armhf Andreas Enge
2020-09-09 9:11 ` Mathieu Othacehe
2020-09-09 9:14 ` Mathieu Othacehe
2020-09-14 9:32 ` Andreas Enge
2020-09-14 13:24 ` Efraim Flashner [this message]
2020-09-14 17:18 ` Andreas Enge
2020-09-17 12:13 ` Mathieu Othacehe
2020-09-17 15:01 ` Andreas Enge
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=20200914132419.GA17272@E5400 \
--to=efraim@flashner.co.il \
--cc=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=othacehe@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.
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).