From: zimoun <zimon.toutoune@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: Christopher Rodriguez <yewscion@gmail.com>,
54864@debbugs.gnu.org,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#54864: GNU Cuirass reports arm64 as armhf
Date: Tue, 26 Apr 2022 13:13:27 +0200 [thread overview]
Message-ID: <CAJ3okZ3VRSBtrDjsEsjdhdfcSTwo+Ptip4mCJDppJirOUGizsQ@mail.gmail.com> (raw)
In-Reply-To: <87fsm0wa5k.fsf@gnu.org>
Hi,
On Tue, 26 Apr 2022 at 10:00, Mathieu Othacehe <othacehe@gnu.org> wrote:
> > I've had this experience before, it's very confusing (it goes on trying
> > to build a toolchain for something that is sure to fail). Perhaps we
> > could at least have a place to refer to in the manual for the common GNU
> > triplets which make the most sense in for GNU Guix (e.g., the currently
> > supported GNU system triplets). Currently I grep the manual for
> > disparate examples when my memory fail me.
[...]
> * Define all the supported architectures in (gnu platforms). We already
> have ARM and Hurd defined there.
>
> * Define %supported-systems and %supported-targets lists constructed by
> parsing the <platform> records.
>
> * Use those lists to check the values passed to --system and --target
> arguments.
>
> * Add --list-available-systems and --list-available-targets arguments
> for all the commands supporting --system and --target arguments.
I agree. It would ease the dance.
In addition, it would help to have a subsection in the manual about
"cross-compilation"; maybe under the Development section. For
instance, I do not find clear the difference between 'system' and
'target'. And the explanations for the triplet are outside the Guix
manual, pointing to [1] which I do not find very clear. Something
like an explicit list of possible values for this triplet would be
worth.
1: <https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/autoconf.html#Specifying-target-triplets>
Cheers,
simon
next prev parent reply other threads:[~2022-04-26 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 21:55 bug#54864: GNU Cuirass reports arm64 as armhf Christopher Rodriguez
2022-04-11 23:47 ` Bengt Richter
2022-04-11 23:57 ` bug#54864: [Pending Patch] Christopher Rodriguez
2022-04-12 13:31 ` bug#54864: Also, [BUG] Christopher Rodriguez
2022-04-20 19:55 ` bug#54864: GNU Cuirass reports arm64 as armhf Ludovic Courtès
2022-04-22 1:33 ` Christopher Rodriguez
2022-04-22 4:28 ` Maxim Cournoyer
2022-04-26 7:56 ` Mathieu Othacehe
2022-04-26 11:13 ` zimoun [this message]
2022-04-27 21:52 ` Ludovic Courtès
2022-04-27 21:37 ` 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=CAJ3okZ3VRSBtrDjsEsjdhdfcSTwo+Ptip4mCJDppJirOUGizsQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=54864@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=othacehe@gnu.org \
--cc=yewscion@gmail.com \
/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).