On Wed, Jan 10, 2024 at 10:45:09AM +0000, Guillaume Le Vaillant wrote:
> Efraim Flashner <efraim@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?

No need to wait for riscv64 for sbcl.

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