unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 68321@debbugs.gnu.org, Munyoki Kilyungi <me@bonfacemunyoki.com>,
	Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
	Benjamin Slade <slade@lambda-y.net>, jgart <jgart@dismail.de>,
	"Paul A. Patience" <paul@apatience.com>
Subject: [bug#68321] Request for merging "lisp-team" branch
Date: Mon, 8 Jan 2024 20:12:13 +0200	[thread overview]
Message-ID: <ZZw6_eWSW4LQ7FyU@3900XT> (raw)
In-Reply-To: <87ttno3qp2.fsf@kitej>


[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]

On Mon, Jan 08, 2024 at 01:06:30PM +0000, Guillaume Le Vaillant wrote:
> The main update of the branch is sbcl 2.4.0.
> 
> The CI built it fine for x86-64 and i686, but has not tried yet on
> other architectures (after several days jobs are still in "scheduled"
> state).
> 
> If you can, please test the branch and report any issue here.

I have sbcl@2.4.0 from the lisp-team branch failing to build on
powerpc64le and succeeding on aarch64-linux.

riscv64-linux failed for me too:

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



-- 
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 #1.2: f04vl4bdrzq6qii23vs76cbc9f2ism-sbcl-2.4.0.drv.gz --]
[-- Type: application/x-gunzip, Size: 50469 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-01-08 18:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 13:06 [bug#68321] Request for merging "lisp-team" branch Guillaume Le Vaillant
2024-01-08 18:12 ` Efraim Flashner [this message]
2024-01-09  0:35   ` Paul A. Patience
2024-01-09 14:10     ` Guillaume Le Vaillant
2024-01-09 16:59       ` Efraim Flashner
2024-01-09 17:36       ` Efraim Flashner
2024-01-09 20:24       ` Efraim Flashner
2024-01-10 10:45         ` Guillaume Le Vaillant
2024-01-10 11:01           ` Efraim Flashner
2024-01-10 13:08             ` Guillaume Le Vaillant
2024-01-10 22:10               ` Guillaume Le Vaillant
2024-01-11 13:50 ` 郑俊杰
2024-01-11 13:57   ` Guillaume Le Vaillant
2024-01-11 17:07     ` bug#68321: " 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=ZZw6_eWSW4LQ7FyU@3900XT \
    --to=efraim@flashner.co.il \
    --cc=68321@debbugs.gnu.org \
    --cc=cox.katherine.e+guix@gmail.com \
    --cc=glv@posteo.net \
    --cc=jgart@dismail.de \
    --cc=me@bonfacemunyoki.com \
    --cc=paul@apatience.com \
    --cc=slade@lambda-y.net \
    /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).