From: dan <i@dan.games>
To: David Elsing <david.elsing@posteo.net>
Cc: dev@jpoiret.xyz, Mathieu Othacehe <othacehe@gnu.org>,
ludo@gnu.org, efraim@flashner.co.il, 66866@debbugs.gnu.org,
janneke@gnu.org
Subject: bug#66866: aarch64 system cross compilation + pinebook pro image broken?
Date: Thu, 11 Apr 2024 12:59:34 +0800 (GMT+08:00) [thread overview]
Message-ID: <912866e9-7775-484f-8ee6-18eab30cbf36@dan.games> (raw)
In-Reply-To: <86frvtvt70.fsf@posteo.net>
Hi David,
Thanks for the reply.
Apr 11, 2024 04:50:03 David Elsing <david.elsing@posteo.net>:
>> Can we put everything inside build-inputs? From my understanding,
>> copy-build-system shouldn't care about cross-compilation at all.
> I understand it that way too. In guix/build-system.scm, it is mentioned
> that build/host/target are used in the sense of the GNU toolchain [1].
> There, "build" is the system used for building and "host" is the target
> system for which the package is built. I guess this was confused when
> copy-build-system was added [2].
Then I think I can submit a patch to guix-patches, hoping to bring more
attention to this bug.
next prev parent reply other threads:[~2024-04-11 5:01 UTC|newest]
Thread overview: 14+ 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
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 [this message]
2024-05-01 21:39 ` bug#66866: Grafting breaks cross-compilation Ludovic Courtès
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
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=912866e9-7775-484f-8ee6-18eab30cbf36@dan.games \
--to=i@dan.games \
--cc=66866@debbugs.gnu.org \
--cc=david.elsing@posteo.net \
--cc=dev@jpoiret.xyz \
--cc=efraim@flashner.co.il \
--cc=janneke@gnu.org \
--cc=ludo@gnu.org \
--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 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).