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

Bug#954031: marked as done (sbcl: Please allow building with clisp on currently unsupported architectures)



Your message dated Wed, 01 Apr 2020 18:34:20 +0000
with message-id <E1jJiBw-000IVI-Kb@fasolo.debian.org>
and subject line Bug#954031: fixed in sbcl 2:2.0.3-1
has caused the Debian Bug report #954031,
regarding sbcl: Please allow building with clisp on currently unsupported architectures
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.)


-- 
954031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954031
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: sbcl
Severity: normal
Tags: patch

Hi!

In order to provide some basic level of continuous integration for
sbcl upstream, it would be great if the sbcl package could be tried
to build on any of the currently unsupported architectures using
clisp.

sbcl has partial support for alpha, hppa, mips*, ppc64 and riscv64
and if we try to build sbcl on any architecture using clisp, we will
be able to provide upstream with a build log of sbcl on any architecture
that might be supported in the future (like ppc64 and riscv64) or
was previously supported and is currently broken (like alpha and hppa).

The attached patch enables building with clisp on all unsupported
architectures.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
diff -Nru old/sbcl-2.0.2/debian/control new/sbcl-2.0.2/debian/control
--- old/sbcl-2.0.2/debian/control	2020-03-07 09:45:04.000000000 +0100
+++ new/sbcl-2.0.2/debian/control	2020-03-16 01:08:41.739735423 +0100
@@ -7,7 +7,8 @@
 Priority: optional
 Build-Depends: debhelper-compat (= 12),
                debhelper (>= 12.8~),
-               sbcl,
+               clisp [!amd64 !arm64 !armhf !i386 !powerpc !ppc64el],
+               sbcl [amd64 arm64 armhf i386 powerpc ppc64el],
                sbcl-source,
                texinfo,
                zlib1g-dev,
diff -Nru old/sbcl-2.0.2/debian/rules new/sbcl-2.0.2/debian/rules
--- old/sbcl-2.0.2/debian/rules	2020-03-07 10:05:22.000000000 +0100
+++ new/sbcl-2.0.2/debian/rules	2020-03-16 00:52:53.830038807 +0100
@@ -4,6 +4,10 @@
 
 export DH_VERBOSE=1
 
+ifeq (,$(filter amd64 arm64 armhf i386 powerpc ppc64el, $(DEB_HOST_ARCH)))
+	BOOTSTRAPLISP := clisp
+endif
+
 ifeq (,$(BOOTSTRAPLISP))
 	BOOTSTRAPLISP := /usr/bin/sbcl --disable-debugger --no-sysinit --no-userinit
 endif

--- End Message ---
--- Begin Message ---
Source: sbcl
Source-Version: 2:2.0.3-1
Done: =?utf-8?q?S=C3=A9bastien_Villemot?= <sebastien@debian.org>

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 954031@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot <sebastien@debian.org> (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, 01 Apr 2020 18:51:36 +0200
Source: sbcl
Architecture: source
Version: 2:2.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team <debian-common-lisp@lists.debian.org>
Changed-By: Sébastien Villemot <sebastien@debian.org>
Closes: 939453 954031 955338
Changes:
 sbcl (2:2.0.3-1) unstable; urgency=medium
 .
   * New upstream release
   * Drop powerpc-ppc64el-fix-LINKFLAGS.patch, no longer needed
   * kfreebsd-linkflags.patch: new patch by John Paul Adrian Glaubitz,
     fixes FTBFS on kfreebsd-amd64 (Closes: #955338)
   * Try to build with clisp by default on archs for which sbcl has not
     yet been bootstrapped. Thanks to John Paul Adrian Glaubitz
     (Closes: #954031)
   * hppa.patch: new patch, fixes architecture detection on hppa
   * d/rules: fix architecture detection on ppc64 (Closes: #939453)
Checksums-Sha1:
 a3e0643e13852fa814bde1a5c49ac6c7bb9a7325 2463 sbcl_2.0.3-1.dsc
 6c3495c803802bb081d76224c30039724ff9ec49 6489521 sbcl_2.0.3.orig.tar.bz2
 3883b9584e434b979d91bc403386fc2644d101bf 75748 sbcl_2.0.3-1.debian.tar.xz
 1e82453d98844118929357fdc69ee0b9898b005e 10097 sbcl_2.0.3-1_amd64.buildinfo
Checksums-Sha256:
 887a1a7a4fab992f5752db070bb3bc51d413a6745cdb5a33ab50ad650d99ef45 2463 sbcl_2.0.3-1.dsc
 b5543f123214b2023ff5fc32dfd00b6cfeabd92c8edb33ad208842c4fd642f00 6489521 sbcl_2.0.3.orig.tar.bz2
 37eb97e923d2f4e93e68a09359da33f559381b8739d33545c821d6bd5a57fee9 75748 sbcl_2.0.3-1.debian.tar.xz
 f6e80688694521911dc847d67fdccb48ceba2ff2c50805a92347eee9c3a389ff 10097 sbcl_2.0.3-1_amd64.buildinfo
Files:
 789944404a920382025690aee919d896 2463 lisp optional sbcl_2.0.3-1.dsc
 37df91288b395717498a6dfea66fc0c1 6489521 lisp optional sbcl_2.0.3.orig.tar.bz2
 23964a272b934bc51ed9fefd0e8224b9 75748 lisp optional sbcl_2.0.3-1.debian.tar.xz
 c9aa7886eef6a938ee810307e21682eb 10097 lisp optional sbcl_2.0.3-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl6E2oUACgkQLOzpNQ7O
vkq6rg/9FH7EURjsxuYDUXnt1E+4tr4iCaiCy3nN88cpLDRR5aI7tT6quRDqcGF6
gJOimkQW3Jy7/HcmJZdkN+8maaf1dLDXKDitS1z+k46FhDPWnwi1AM/BzYgHfqsK
KdYOEHatAbd84MLj67OFdugbrwzmJ64Av3aD20Bt43H6BzfNkl5FT59iOP3aUhdv
9r4Ph/8P5NjMRGwFE5iK//XCtuPclHHLJrvCO7vfvTT0gBX0XXyUBlT/Y765nnBL
JQ0jNBYYEQNtNLj4nkYWnlBxVmhgBfZAHDE2P42Rm5uElbPRvOZRAQkO09goqoEn
D+IsaYIvqducwWQYPLYo/53Ab57cShcn+qaD3h8L7DBeIKUIlC9G4fu1NyddqLSp
mkZRtkhGqJij6jSfsEXlwqPgvqxOHsYOodiHFLuUQv1GfhD9YuktlKLJtl01NA3/
BZUOSFwxEgocPBrzPeVlmLDeg0FZmUX1BxAxWI6IBGG5Esg6l0qQ0eNbgLp5Axa2
E2y/vZpJPMxR2XEgeF7KXzw+X1ER1qiZAoJQ5eRny+kahe1GyXm002W6wVKy/hKE
vJAypwL4Jmc61H7hvzKs/wcnTGQ/RpAE9m8JeYnu9JrmmJI2+mHiDpmVu7vHOi1m
4kocHAOkRTpG14C4Ih/qEPUM3w6kRlWzogYiCCl4wZWph24/i6s=
=dNyT
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: