[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1033731: marked as done (sbcl: support bootstrap on riscv64)



Your message dated Wed, 13 Nov 2024 11:52:26 +0000
with message-id <E1tBBv8-00ApLv-U6@fasolo.debian.org>
and subject line Bug#1033731: fixed in sbcl 2:2.4.10-2
has caused the Debian Bug report #1033731,
regarding sbcl: support bootstrap on riscv64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1033731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033731
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: sbcl
Version: 2:2.2.9- 1
Severity: minor
Tags: ftbfs
User: debian-riscv@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-riscv@lists.debian.org

Dear Maintainer ,

The sbcl can be bootstraped on Debian riscv64 now.
A riscv64 sbcl package is available here:
https://drive.google.com/drive/folders/1wCCV6Ke0YMCrgGwKF4rjTTlEz8wr4Piq?usp=share_link

Please note it is 2.2.2 from upstream to be bootstrapped. At first
used 2.3.2, but due to one commit[0] was introduced after 2.2.3:
was failed to bootstrap it after many attempts
There are many issues 0n Debian using ecl to bootstrap it also.
| So with help of Christoph[1], I first built sbcl in a cross build
way then patched the binary file into sbcl package which can be
bootstrapped itself at last.

I hope it can reduce bootstrap pain on Debian r iscv64. And
I will also keep an eye on upstream changes and update here.
BTW, I have to modify the d/rules file to fix the issue that reported
cannot find `stage1/bin/sbcl` issue. It seems the file was cleared by
`./clean.sh` even with `chmod 100 stage 1`

[0]: https://bugs.launchpad.net/sbcl/+bug/2002930
[1]: https://lists.debian.org/debian-common-lisp/2023/03/msg00005.html

BR,
Bo

--- End Message ---
--- Begin Message ---
Source: sbcl
Source-Version: 2:2.4.10-2
Done: Sean Whitton <spwhitton@spwhitton.name>

We believe that the bug you reported is fixed in the latest version of
sbcl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1033731@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sean Whitton <spwhitton@spwhitton.name> (supplier of updated sbcl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 13 Nov 2024 18:57:27 +0800
Source: sbcl
Architecture: source
Version: 2:2.4.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team <debian-common-lisp@lists.debian.org>
Changed-By: Sean Whitton <spwhitton@spwhitton.name>
Closes: 1033731
Changes:
 sbcl (2:2.4.10-2) unstable; urgency=medium
 .
   [ Bo YU ]
   * Switch riscv64 to bootstrap with clisp (Closes: #1033731).
Checksums-Sha1:
 b63ea49a58a30a722a62da6c9f6f7c695ccbf92a 2577 sbcl_2.4.10-2.dsc
 db507c503f1e7f0175860abf26d1e9d4930f64c5 78960 sbcl_2.4.10-2.debian.tar.xz
Checksums-Sha256:
 08429fe9b810be9b40a22b8d1e63a613398b42e21c3ecf32021c1d6950e42302 2577 sbcl_2.4.10-2.dsc
 0069c0a6e53713c7329e0b16249ba15869154c47e22a183e0f2711616955e507 78960 sbcl_2.4.10-2.debian.tar.xz
Files:
 87c127c2b7089b439f36403abf3cdd72 2577 lisp optional sbcl_2.4.10-2.dsc
 5d0591f294a3548bd0945fd7109714c2 78960 lisp optional sbcl_2.4.10-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmc0iwUACgkQaVt65L8G
YkAxJA/9GJHEk6SsycSQ64dObii8vDQ1uA/IuCA/64nJW+WvfXXVYy7UVDgKFg7s
unOwkBuH2oaF8Fm+V2+tOc++TKweuhVhUKqqX487LNWQsRr/pLd5PDYaP1wjHwK0
I03uesHKviV9buJQVu05hKyHaz8LnGYMdOgZT/pQT5Um2LcXVo/Fuel15KyD00JZ
mQntQkm4HAnYZyRVuiQJQFOW16PMBmejvAZeZlWQaE1Le+9xuP/6OEhggyru9850
KaikMKjmOAJMvaaF+xZU+t0VzGobrsmYVvTvXnnpKhmH2J5ht/60YggWmF922jKL
VIx/3wHZj0TJWjBfI9rWDQUa67EgdTQpCfBi7ThQ3n/BoZhf1J5+gheEFuOoqdRq
f7vn3ZAU4l4+DAH2jkZsLE5KaIfs7B9tFshqA/wjbr5Mj2D3KqexpfD9g6KGI3xc
GZzuIxGlOWQYd3nV9zGrKWMEJjT+ly2fnt5oEpMEDyiNrSKM+S3G4lS/y69QrnxJ
2vhcyQVoFyPBqkL0FSnpcm25e1Sy3w28ADO5OkK6y41x+eXMunpj2sqLS3FV2ceF
HCdFUNXl/Ibv24hoY4jflPACFZ0N47zTFm0JfJmqxV8GSMRLpM9XqeP6J2Qd+8Dm
joHW2DTR2y07vCgatyljO52RG0F/kpvnf4cL1iGswCUbiN9nfHY=
=gTqi
-----END PGP SIGNATURE-----

Attachment: pgp8I4hzV5B4C.pgp
Description: PGP signature


--- End Message ---

Reply to: