unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"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: Mon, 9 May 2022 11:57:01 +0300	[thread overview]
Message-ID: <YnjXXesbodCxPt17@3900XT> (raw)
In-Reply-To: <YnjUbBWxpVMnANHc@3900XT>

[-- Attachment #1: Type: text/plain, Size: 2134 bytes --]

On Mon, May 09, 2022 at 11:44:28AM +0300, Efraim Flashner wrote:
> On Mon, May 09, 2022 at 12:14:50AM +0200, Ludovic Courtès wrote:
> > 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/
> 
> I have a WIP patch for adding CPU detection for aarch64. Perhaps it'll
> help with the issues?

(ins)[efraim@pbp guix]$ ./pre-inst-env guix shell --export-manifest gsl openblas gcc-toolchain --tune
;;; note: source file /home/efraim/workspace/guix/guix/cpu.scm
;;;       newer than compiled /home/efraim/workspace/guix/guix/cpu.go

;;; ("aarch64" #f #f #f #<<set> vhash: #<vhash 1602dca0 9 pairs> insert: #<procedure %insert (t-5ce36f5c768e728-317 t-5ce36f5c768e728-319)> ref: #<procedure vhash-assoc (key vhash #:optional equal? hash)>>)
hint: Consider passing the `--check' option once to make sure your shell does not clobber environment variables.

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"))))


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-05-09  8:59 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 [this message]
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=YnjXXesbodCxPt17@3900XT \
    --to=efraim@flashner.co.il \
    --cc=55283@debbugs.gnu.org \
    --cc=ludo@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).