From: Efraim Flashner <efraim@flashner.co.il>
To: Guillaume Le Vaillant <glv@posteo.net>, guix-devel@gnu.org
Subject: Re: CI job for lisp-team branch
Date: Thu, 7 Sep 2023 15:17:36 +0300 [thread overview]
Message-ID: <ZPm_YPqePLavuQY9@pbp> (raw)
In-Reply-To: <ZPh0xQvgfY1AYm7b@pbp>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Wed, Sep 06, 2023 at 03:47:01PM +0300, Efraim Flashner wrote:
> On Mon, Sep 04, 2023 at 09:27:44AM +0000, Guillaume Le Vaillant wrote:
> > Hi.
> > I created a lisp-team branch to work one some updates for clisp and
> > sbcl. Could someone with admin access to the CI things add a job for it?
> > Thanks.
>
> 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.
--
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-07 12:18 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 [this message]
2023-09-07 12:31 ` Guillaume Le Vaillant
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZPm_YPqePLavuQY9@pbp \
--to=efraim@flashner.co.il \
--cc=glv@posteo.net \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).