From: Christopher Rodriguez <yewscion@gmail.com>
To: 54864@debbugs.gnu.org
Subject: bug#54864: GNU Cuirass reports arm64 as armhf
Date: Mon, 11 Apr 2022 17:55:41 -0400 [thread overview]
Message-ID: <pkmp4eczhn9sir.fsf@crane.ant.amazon.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
Reporting this from my local installs of GNU Cuirass, though a cursory glance at
ci.guix.gnu.org (likely) shows the same issue:
GNU Cuirass currently reports both `armhf-linux` and `arm64-linux` targets as
`armhf-linux` on the web interface.
This is not only incorrect, but potentially confusing to newcomers: I have spent
some free time in the last week or two (after purchasing an MNT Reform) trying
to get my home server to build packages for deployment on an ARM-based laptop. I
only discovered that I was targeting the 32-bit version of ARM after asking on
IRC (and then looking through the logs:
https://logs.guix.gnu.org/guix/2022-04-11.log#221203 or thereabouts, where
vagrantc mentions `armhf` as suffering bitrot and goes on to mention both
`aarch64` and `arm64` in another sentence).
This is not helped by the Documentation
(https://guix.gnu.org/cuirass/manual/cuirass.html#Specifications) not giving any
examples of supported platforms, highly-search-engine-ranked issues and blog
posts (https://issues.guix.gnu.org/54055 and
https://guix.gnu.org/en/blog/2021/cuirass-10-released/ for instance, both
front-page google) only mentioning `armhf-linux`, and all running instances of
GNU Cuirass not even listing `arm64-linux` as an option.
When I have time (I am out of town for the rest of the week) I will try to
submit a patch for the documentation to list the available targets. Changing the
UI is more complex (though wider-reaching) and a bit more out of my
wheelhouse. Help there would be appreciated.
--
Christopher Rodriguez
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2022-04-11 22:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 21:55 Christopher Rodriguez [this message]
2022-04-11 23:47 ` bug#54864: GNU Cuirass reports arm64 as armhf 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
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=pkmp4eczhn9sir.fsf@crane.ant.amazon.com \
--to=yewscion@gmail.com \
--cc=54864@debbugs.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).