unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: raingloom <raingloom@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 55283@debbugs.gnu.org
Subject: bug#55283: ‘tests/guix-shell-export-manifest.sh’ fails on aarch64-linux
Date: Fri, 6 May 2022 02:28:26 +0200	[thread overview]
Message-ID: <20220506022826.5089eb2c@riseup.net> (raw)
In-Reply-To: <87ee1761ci.fsf@inria.fr>

On Fri, 06 May 2022 00:50:21 +0200
Ludovic Courtès <ludo@gnu.org> wrote:

> The log goes like this:
> ...
> + guix shell --export-manifest gsl openblas gcc-toolchain --tune

This seems to be the important part, it looks like the CPU arch isn't
being detected.

> Backtrace:
> In ice-9/boot-9.scm:
>   1752:10 13 (with-exception-handler _ _ #:unwind? _ # _)
> In unknown file:
>           12 (apply-smob/0 #<thunk 5bd2e0>)
> In ice-9/boot-9.scm:
>     724:2 11 (call-with-prompt _ _ #<procedure
> default-prompt-handle…>) In ice-9/eval.scm:
>     619:8 10 (_ #(#(#<directory (guile-user) 5c2c80>)))
> In guix/ui.scm:
>    2230:7  9 (run-guix . _)
>   2193:10  8 (run-guix-command _ . _)
> In guix/scripts/shell.scm:
>    160:17  7 (guix-shell . _)
> In ice-9/boot-9.scm:
>   1747:15  6 (with-exception-handler #<procedure 4bd7b0 at ice-9/bo…>
> …) In srfi/srfi-37.scm:
>    201:16  5 (next-arg)
>    113:18  4 (invoke-option-processor _ _ _ _ _)
> In unknown file:
>            3 (_ #<procedure 4bd660 at srfi/srfi-37.scm:114:22 ()> # #)
>            2 (_ #<procedure 9aa9c0 at ice-9/boot-9.scm:798:28 ()> # #)
> In guix/transformations.scm:
>    864:25  1 (_ _ _ _ ((package ad-hoc-package "gcc-toolchain") (…)
> …)) In guix/cpu.scm:
>      94:2  0 (cpu->gcc-architecture #f)

This indicates the same to me.
But I don't know the internals of --tune well enough, so it's just a
hunch.

> guix/cpu.scm:94:2: In procedure cpu->gcc-architecture:
> In procedure struct-vtable: Wrong type argument in position 1
> (expecting struct): #f
> + rm -r t-guix-manifest-12319
> FAIL tests/guix-shell-export-manifest.sh (exit status: 1)
> --8<---------------cut here---------------end--------------->8---
> 
> This is ca. 312879fddcf0713c0f1dafcc6faa089edbbb6e04.
> 
> Ludo’.




  reply	other threads:[~2022-05-06  0:29 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 [this message]
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
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=20220506022826.5089eb2c@riseup.net \
    --to=raingloom@riseup.net \
    --cc=55283@debbugs.gnu.org \
    --cc=ludo@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).