From: "Sébastien Lerique" <sl@eauchat.org>
To: 55283@debbugs.gnu.org
Subject: bug#55283: ‘tests/guix-shell-export-manifest.sh’ fails on aarch64-linux
Date: Mon, 09 May 2022 21:04:23 +0900 [thread overview]
Message-ID: <87zgjqc2p2.fsf@eauchat.org> (raw)
In-Reply-To: <87ee1761ci.fsf@inria.fr>
Hello all,
> I have a WIP patch for adding CPU detection for aarch64. Perhaps it'll
> help with the issues?
>
Just confirming this works on rock64.
---
sl@matrixbox ~/guix [env]$ ./pre-inst-env guix shell --export-manifest gsl openblas gcc-toolchain --tune
;;; ("aarch64" #f #f #f #<<set> vhash: #<vhash 8d0ff60 9 pairs> insert: #<procedure %insert (t-5ce36f5c768e728-317 t-5ce36f5c768e728-319)> ref: #<procedure vhash-assoc (key vhash #:optional equal? hash)>>)
guix shell: tuning gsl@2.7 for CPU armv8-a
;; What follows is a "manifest" equivalent to the command line you gave.
;; You can store it in a file that you may then pass to any 'guix' command
;; that accepts a '--manifest' (or '-m') option.
(use-modules (guix transformations))
(define transform1
(options->transformation '((tune . "armv8-a"))))
(packages->manifest
(list (transform1 (specification->package "gsl"))
(transform1 (specification->package "openblas"))
(transform1
(specification->package "gcc-toolchain"))))
---
In case this is still useful, on the same rock64 /proc/cpuinfo is:
sl@matrixbox ~$ cat /proc/cpuinfo
processor : 0
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 2
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 3
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Cheers!
Sébastien
next prev parent reply other threads:[~2022-05-10 13:36 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
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 [this message]
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=87zgjqc2p2.fsf@eauchat.org \
--to=sl@eauchat.org \
--cc=55283@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).