unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: raingloom <raingloom@riseup.net>, "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, 06 May 2022 23:12:33 +0200	[thread overview]
Message-ID: <5d219586c7a9a5ed2d89b12db73385d9d55adeb9.camel@telenet.be> (raw)
In-Reply-To: <20220506022826.5089eb2c@riseup.net>

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

raingloom schreef op vr 06-05-2022 om 02:28 [+0200]:
> > …)) 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.

Could anyone who encounters the issue on aarch64-linux send their
/proc/cpuinfo, such that other people can test the body of 'current-
cpu' on that copy?

Also, why doesn't 'current-cpu' throw some kind of exception instead of
#false?  No users of 'current-cpu' appear to handle #false and
returning #false is not documented in the docstring.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-05-06 21:13 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 [this message]
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=5d219586c7a9a5ed2d89b12db73385d9d55adeb9.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55283@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=raingloom@riseup.net \
    /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).