From: Mathieu Othacehe <othacehe@gnu.org>
To: dan <i@dan.games>
Cc: "Josselin Poiret" <dev@jpoiret.xyz>,
"Jan Nieuwenhuizen" <janneke@gnu.org>,
"Ludovic Courtès" <ludo@gnu.org>,
"Efraim Flashner" <efraim@flashner.co.il>,
66866@debbugs.gnu.org
Subject: bug#66866: aarch64 system cross compilation + pinebook pro image broken?
Date: Sat, 13 Jan 2024 19:41:51 +0100 [thread overview]
Message-ID: <87ttnh5b4g.fsf@gnu.org> (raw)
In-Reply-To: <871qal6ruc.fsf@gnu.org> (Mathieu Othacehe's message of "Sat, 13 Jan 2024 18:55:23 +0100")
> The issue seems to be that grafting ends-up dragging the bootstrap
> packages into the closure when cross-compiling which is quite scary.
I could narrow it down somehow.
This commands drags the bootstrap and fails:
--8<---------------cut here---------------start------------->8---
guix build --target=<any-target> alsa-lib
--8<---------------cut here---------------end--------------->8---
while this one doesn't:
--8<---------------cut here---------------start------------->8---
guix build --target=<any-target> alsa-lib --no-grafts
--8<---------------cut here---------------end--------------->8---
Not sure how to go further. Adding Ludo and Efraim.
Thanks,
Mathieu
next prev parent reply other threads:[~2024-01-13 19:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 1:55 bug#66866: aarch64 system cross compilation + pinebook pro image broken? Denis 'GNUtoo' Carikli
2023-11-06 17:55 ` dan
2023-11-09 11:41 ` Josselin Poiret via Bug reports for GNU Guix
2023-11-09 12:23 ` dan
2024-01-03 9:05 ` Mathieu Othacehe
2024-01-13 17:55 ` Mathieu Othacehe
2024-01-13 18:41 ` Mathieu Othacehe [this message]
2024-02-11 19:34 ` David Elsing
2024-03-18 17:30 ` dan
2024-04-10 6:44 ` dan
2024-04-10 20:49 ` David Elsing
2024-04-11 4:59 ` dan
2024-05-01 21:39 ` bug#66866: Grafting breaks cross-compilation Ludovic Courtès
2024-05-12 15:39 ` [bug#70492] " David Elsing
2023-12-31 13:23 ` bug#66866: aarch64 system cross compilation + pinebook pro image broken? Lars Rustand
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=87ttnh5b4g.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=66866@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=efraim@flashner.co.il \
--cc=i@dan.games \
--cc=janneke@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 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.