From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 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: Mon, 09 May 2022 00:14:50 +0200 [thread overview]
Message-ID: <87wnevu0x1.fsf@gnu.org> (raw)
In-Reply-To: <87wney6vwq.fsf@contorta> (Vagrant Cascadian's message of "Fri, 06 May 2022 17:14:45 -0700")
Hi!
Vagrant Cascadian <vagrant@debian.org> skribis:
> Well, I guess I answered my initial question by reading the error
> message... guix/cpu.scm ... how did that work before for things like
> cross-building, where /proc/cpuinfo is *definitely* wrong to get
> information about the architecture you're building for?
(guix cpu) is used when passing ‘--tune’, which is used for native
builds:
https://hpc.guix.info/blog/2022/01/tuning-packages-for-a-cpu-micro-architecture/
Ludo’.
next prev parent reply other threads:[~2022-05-08 22:15 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 [this message]
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
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=87wnevu0x1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=55283@debbugs.gnu.org \
--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).