From: Stefan <stefan-guix@vodafonemail.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 45654@debbugs.gnu.org
Subject: bug#45654: Building guile on x86_64 for aarch64 fails because of a missing guile
Date: Wed, 6 Jan 2021 19:00:58 +0100 [thread overview]
Message-ID: <97F6E0D3-9E54-4290-9743-03A275838F53@vodafonemail.de> (raw)
In-Reply-To: <87pn2ikxc8.fsf@gnu.org>
Hi Ludo’!
Thanks for caring!
> I don’t see why restarting the two services has no effect. Could you
> compare the output of:
>
> guix gc -R $(cat /proc/sys/fs/binfmt_misc/qemu-aarch64 |grep interpreter|cut -d ' ' -f 2-)
>
> with the ‘--chroot-directory’ flags shown by:
>
> cat /proc/$(LC_ALL=C sudo -E herd status guix-daemon | grep Running| sed -'es/.* \([0-9]\+\).*/\1/g')/cmdline | xargs -0 echo
There were no ‘--chroot-directory’ flags in my case. So I wondered what is wrong and re-read the manual. I figured that I managed to copy-paste the ‘wrong’ example code from the “Transparent Emulation with QEMU” section into my operating-system definition, the first one. I was missing (guix-support? #t).
I know that I read the ‘guix-support’ documentation before changing my operating-system. I think in the end I copied the first example, I freshly navigated to the “Transparent Emulation with QEMU” chapter after looking-up something else, maybe also because it is mentioning the aarch64, which I needed.
So now it is working. Thanks again for you support. :-)
Would you accept a patch for the manual to contain (guix-support? #t) in the first example as well?
Actually I would even prefer a default change of ‘guix-support’ to #t.
Would it also possible to print some proper error message, if guix build is used with an unsupported ‘--system’ argument.
Bye
Stefan
next prev parent reply other threads:[~2021-01-06 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 15:32 bug#45654: Building guile on x86_64 for aarch64 fails because of a missing guile Stefan
2021-01-04 18:08 ` Stefan
2021-01-05 12:25 ` Efraim Flashner
2021-01-05 14:55 ` Stefan
2021-01-05 17:20 ` Stefan
2021-01-06 11:14 ` Ludovic Courtès
2021-01-06 11:35 ` Stefan
2021-01-06 13:29 ` Ludovic Courtès
2021-01-06 18:00 ` Stefan [this message]
2021-01-07 8:24 ` Ludovic Courtès
2021-01-07 20:44 ` bug#45654: [PATCH 1/1] gnu: qemu-binfmt-service-type: Change 'guix-support?' default to #t Stefan
2021-01-16 21:39 ` Ludovic Courtès
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=97F6E0D3-9E54-4290-9743-03A275838F53@vodafonemail.de \
--to=stefan-guix@vodafonemail.de \
--cc=45654@debbugs.gnu.org \
--cc=ludo@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).