From: Guillaume Le Vaillant <glv@posteo.net>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: CI job for lisp-team branch
Date: Thu, 07 Sep 2023 12:31:39 +0000 [thread overview]
Message-ID: <87o7iejgxk.fsf@kitej> (raw)
In-Reply-To: <ZPm_YPqePLavuQY9@pbp>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Wed, Sep 06, 2023 at 03:47:01PM +0300, Efraim Flashner wrote:
>>
>> I commented on IRC but figured I should post to the mailing list.
>>
>> I tested sbcl@2.3.8 on riscv64-linux and the build failed in the contrib
>> section. I see the patch was removed, presumably because it was included
>> in the upstream release. When I finish my current build target(s) I'll
>> see what needs to be done there.
>
> Re-adding the patch failed hard when applying the patch. I tested
> downgrading sbcl to 2.3.7 and that built everything without any trouble
> on riscv64-linux.
The patch was a backport from upstream (commit
8704f528f227f587d0e06dfd2f807aeca7a69a71), so it is already in the
sources for sbcl 2.3.8.
What error do you get when building on riscv64? Maybe we could report it
upstream as I have not seen anything about riscv64 fixes in the commit
history of sbcl since version 2.3.8.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2023-09-07 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 9:27 CI job for lisp-team branch Guillaume Le Vaillant
2023-09-04 9:46 ` 宋文武
2023-09-05 1:52 ` Maxim Cournoyer
2023-09-05 8:44 ` Guillaume Le Vaillant
2023-09-06 12:47 ` Efraim Flashner
2023-09-07 12:17 ` Efraim Flashner
2023-09-07 12:31 ` Guillaume Le Vaillant [this message]
2023-09-07 12:46 ` Efraim Flashner
2023-09-07 13:49 ` Guillaume Le Vaillant
2023-09-12 15:46 ` Guillaume Le Vaillant
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7iejgxk.fsf@kitej \
--to=glv@posteo.net \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.