From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Vagrant Cascadian <vagrant@debian.org>,
55283@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>,
raingloom <raingloom@riseup.net>
Subject: bug#55283: ‘tests/guix-shell-export-manifest.sh’ fails on aarch64-linux
Date: Tue, 10 May 2022 17:43:43 +0200 [thread overview]
Message-ID: <87r151pf4g.fsf@gnu.org> (raw)
In-Reply-To: <87v8udpf9v.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 10 May 2022 17:40:28 +0200")
Ludovic Courtès <ludo@gnu.org> skribis:
> (The bug reported at the beginning of this thread looks rather basic
> though; I’ll follow up on that.)
Actually no. :-)
I guess the first hunk of your patch, which modifies ‘current-cpu’ so
that it does not return #f on AArch64, is the actual fix (it can be a
patch of its own).
The second hunk, which modifies ‘cpu->gcc-architecture’, is an
enhancement.
Ludo’.
next prev parent reply other threads:[~2022-05-10 15:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 22:50 bug#55283: ‘tests/guix-shell-export-manifest.sh’ fails on aarch64-linux Ludovic Courtès
2022-05-06 0:28 ` raingloom
2022-05-06 20:43 ` Vagrant Cascadian
2022-05-06 21:12 ` Maxime Devos
2022-05-06 22:13 ` Vagrant Cascadian
2022-05-07 0:14 ` Vagrant Cascadian
2022-05-07 0:45 ` Vagrant Cascadian
2022-05-08 22:14 ` Ludovic Courtès
2022-05-09 8:44 ` Efraim Flashner
2022-05-09 8:57 ` Efraim Flashner
2022-05-09 10:03 ` Maxime Devos
2022-05-09 14:17 ` Efraim Flashner
2022-05-10 15:40 ` Ludovic Courtès
2022-05-10 15:43 ` Ludovic Courtès [this message]
2022-05-10 15:55 ` Efraim Flashner
2022-05-10 15:50 ` Efraim Flashner
2022-05-12 8:09 ` Ludovic Courtès
2022-05-09 12:04 ` Sébastien Lerique
2022-05-09 12:32 ` Sébastien Lerique
2022-05-17 12:29 ` Efraim Flashner
2022-05-17 15:01 ` Pavel Shlyak
2022-05-17 16:38 ` Pavel Shlyak
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=87r151pf4g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=55283@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=maximedevos@telenet.be \
--cc=raingloom@riseup.net \
--cc=vagrant@debian.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).