From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Stefan <stefan-guix@vodafonemail.de>, 45654@debbugs.gnu.org
Subject: bug#45654: Building guile on x86_64 for aarch64 fails because of a missing guile
Date: Wed, 06 Jan 2021 12:14:32 +0100 [thread overview]
Message-ID: <87v9cami5j.fsf@gnu.org> (raw)
In-Reply-To: <X/RavzutNlbnIc2W@3900XT> (Efraim Flashner's message of "Tue, 5 Jan 2021 14:25:35 +0200")
Hi,
Efraim Flashner <efraim@flashner.co.il> skribis:
>> while setting up the build environment: executing `/gnu/store/x3gq648qnfnla7nppyfjvj62s2i8y7rl-guile-3.0.2/bin/guile': No such file or directory
[...]
> I just came across this today myself. try 'sudo herd restart
> guix-daemon'. It's what made it suddenly start working for me (I
> reconfigured to add qemu-binfmt service without restarting).
For the record, this is necessary because when you reconfigure,
qemu-binfmt might set store file names that differ from those passed as
‘--chroot-directory’ options to guix-daemon.
To make sure both are in sync:
sudo herd restart qemu-binfmt
sudo herd restart guix-daemon
Stefan: I recommend against ‘--disable-chroot’ as anything could leak
into build processes.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-01-06 11:15 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 [this message]
2021-01-06 11:35 ` Stefan
2021-01-06 13:29 ` Ludovic Courtès
2021-01-06 18:00 ` Stefan
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=87v9cami5j.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=45654@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=stefan-guix@vodafonemail.de \
/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).