GNU bug report logs - #55283
‘tests/guix-shell-export-manifest.sh’ fails on aarch64-linux

Previous Next

Package: guix;

Reported by: Ludovic Courtès <ludo <at> gnu.org>

Date: Thu, 5 May 2022 22:51:02 UTC

Severity: important

Done: Efraim Flashner <efraim <at> flashner.co.il>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Maxime Devos <maximedevos <at> telenet.be>
To: raingloom <raingloom <at> riseup.net>, Ludovic Courtès <ludo <at> gnu.org>
Cc: 55283 <at> 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

[Message part 1 (text/plain, inline)]
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.

[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 3 years and 62 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.