GNU bug report logs - #65592
[PATCH]: Update sbcl to 2.3.8

Previous Next

Full log

View this message in rfc822 format

From: Christopher Baines <mail <at> cbaines.net>
To: Guillaume Le Vaillant <glv <at> posteo.net>
Cc: andremegafone <at> gmail.com, 65592 <at> debbugs.gnu.org, 65592-done <at> debbugs.gnu.org
Subject: [bug#65592] [PATCH]: Update sbcl to 2.3.8
Date: Wed, 27 Sep 2023 11:44:10 +0100

[Message part 1 (text/plain, inline)]

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

> André A. Gomes <andremegafone <at> gmail.com> skribis:
>
>> Guillaume Le Vaillant <glv <at> posteo.net> writes:
>>
>>> SBCL 2.3.8 didn't build on riscv64, so instead version 2.3.7 is used for
>>> now. It has been merged in master at
>>> 4f35ff1275e05be31f5d41464ccf147e9dbfd016.
>>> Let's close this issue and open a new one for a future update of SBCL
>>> (maybe 2.3.9 will fix the build failure).
>>
>> Hi Guillaume,
>>
>> Just for future reference, is there a way for me to check whether a SBCL
>> builds on all platforms when sending a patch?  Thanks.
>
> For x86_64, i686, aarch64, armhf and powerpc64le, you can check on
> <https://qa.guix.gnu.org/issue/ISSUE-NUMBER>.

Note that we're lacking sufficient powerpc64 hardware to do QA for that
architecture.

> However so far the CI doesn't have builds for riscv64, because it
> doesn't have riscv64 hardware. Efraim Flashner <efraim <at> flashner.co.il>
> has a riscv64 board with Guix on it, and he is the one who tried
> building SBCL 2.3.8 and saw the failure.

We do however have RiscV hardware connected to the bordeaux build farm,
I've got a machine and there's also a second connected. We probably need
at least one more machine to enable the system for QA though.

[signature.asc (application/pgp-signature, inline)]

Previous Next

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