From: Christopher Baines <mail@cbaines.net>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, 57215@debbugs.gnu.org
Subject: bug#57215: ci: Fail to evaluate Guix specification
Date: Tue, 16 Aug 2022 09:41:31 +0100 [thread overview]
Message-ID: <87pmh0injd.fsf@cbaines.net> (raw)
In-Reply-To: <87pmh0fwq5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Mathieu Othacehe <othacehe@gnu.org> writes:
> Now there are multiple unclear points to me:
>
> 1. Why do we need an available machine with the foreign architecture to
> compute the corresponding "guix" derivation? Note that the evaluation of
> package derivations for foreign systems works even though a
> corresponding machine is not available:
>
> mathieu@berlin ~$ guix build -s powerpc64le-linux -d hello
> /gnu/store/spzmh79qi21k26p15w27r3jjg95szg17-hello-2.12.1.drv
This has been something I've been interested in as well, since the Guix
Data Service has the same problem when computing these derivations.
I think the latest information I have is set out here:
https://lists.gnu.org/archive/html/guix-devel/2022-02/msg00196.html
So, I think there's some involvement of grafts that mean you end up
building things when just trying to compute the derivation. But that's
as far as I got, I don't really understand why this is the case, or what
can be done about it.
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2022-08-16 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 19:56 bug#57215: ci: Fail to evaluate Guix specification Mathieu Othacehe
2022-08-15 12:01 ` Mathieu Othacehe
2022-08-15 12:48 ` Mathieu Othacehe
2022-08-16 7:56 ` Mathieu Othacehe
2022-08-16 8:41 ` Christopher Baines [this message]
2022-08-16 9:20 ` Mathieu Othacehe
2022-08-16 10:56 ` Christopher Baines
2022-08-19 14:19 ` Maxim Cournoyer
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=87pmh0injd.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=57215@debbugs.gnu.org \
--cc=me@tobias.gr \
--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.
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.