From: "Ludovic Courtès" <ludo@gnu.org>
To: Stefan <stefan-guix@vodafonemail.de>
Cc: 45654@debbugs.gnu.org
Subject: bug#45654: Building guile on x86_64 for aarch64 fails because of a missing guile
Date: Thu, 07 Jan 2021 09:24:06 +0100 [thread overview]
Message-ID: <87pn2hjgt5.fsf@gnu.org> (raw)
In-Reply-To: <97F6E0D3-9E54-4290-9743-03A275838F53@vodafonemail.de> (Stefan's message of "Wed, 6 Jan 2021 19:00:58 +0100")
Hi,
Stefan <stefan-guix@vodafonemail.de> skribis:
> 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).
Ah ha!
> 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.
Yeah, we should probably change the default to #t if nobody disagrees.
The downsides I can see are: (1) changing defaults in general means
breaking user assumptions, and (2) setting ‘guix-support?’ means that
the build environment is no longer completely hermetic (it contains
extra store items), though it’s arguably still very much under control.
Overall, it’s probably OK.
Could you send a patch?
> Would it also possible to print some proper error message, if guix build is used with an unsupported ‘--system’ argum
ent.
I don’t think so: all we get is ENOENT from execve(2). There’s no way
to distinguish this kind of ENOENT from the other kind of ENOENT.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-01-07 8:25 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
2021-01-07 8:24 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn2hjgt5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=45654@debbugs.gnu.org \
--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 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.