GNU bug report logs - #68321
Request for merging "lisp-team" branch

Previous Next

Package: guix-patches;

Reported by: Guillaume Le Vaillant <glv <at> posteo.net>

Date: Mon, 8 Jan 2024 13:24:02 UTC

Severity: normal

Done: Guillaume Le Vaillant <glv <at> posteo.net>

Bug is archived. No further changes may be made.

Full log


Message #26 received at 68321 <at> debbugs.gnu.org (full text, mbox):

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 68321 <at> debbugs.gnu.org, Munyoki Kilyungi <me <at> bonfacemunyoki.com>,
 Katherine Cox-Buday <cox.katherine.e+guix <at> gmail.com>,
 Benjamin Slade <slade <at> lambda-y.net>, jgart <jgart <at> dismail.de>,
 "Paul A. Patience" <paul <at> apatience.com>
Subject: Re: [bug#68321] Request for merging "lisp-team" branch
Date: Wed, 10 Jan 2024 10:45:09 +0000
[Message part 1 (text/plain, inline)]
Efraim Flashner <efraim <at> flashner.co.il> skribis:

> riscv64-linux failure looks similar at first look to the ppc64le failure
>
> "obj/from-xc/src/code/cold-error.lisp-obj"
> "obj/from-xc/src/code/early-full-eval.lisp-obj"
> "obj/from-xc/src/code/debug-var-io.lisp-obj"
> "obj/from-xc/src/code/early-float.lisp-obj" fatal error encountered in SBCL pid 553 tid 553:
> internal error too early in init, can't recover
>
> Error opening /dev/tty: No such device or address
> Internal error #1 "An attempt was made to use an undefined FDEFINITION." at 0x4101560
>     SC: 0, Offset: 28   $1=       0x4f286dff: other pointer
> Welcome to LDB, a low-level debugger for the Lisp runtime environment.
> ldb>
> real    0m0.325s
> user    0m0.066s
> sys     0m0.242s
> error: in phase 'build': uncaught exception:
> %exception #<&invoke-error program: "sh" arguments: ("make.sh" "clisp"
> "--prefix=/gnu/store/wwy4kc4ary627b7igx5cxjsgkl8nq0yv-sbcl-2.4.0"
> "--dynamic-space-size=3072" "--with-sb-core-compression"
> "--with-sb-xref-for-internals" "--without-sb-simd") exit-status: 1 term-signal:
> #f stop-signal: #f>
> phase `build' failed after 10113.1 seconds

I reported the issue on riscv64 upstream
(https://bugs.launchpad.net/sbcl/+bug/2048869).

In case there is no fix for riscv64 right now, do you think we should
block sbcl updates, or should we update it anyway as it works on other
architectures, and hope that riscv64 will work again in the future?
[signature.asc (application/pgp-signature, inline)]

This bug report was last modified 1 year and 189 days ago.

Previous Next


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