Bug#954031: [Sbcl-devel] Bug#954031: sbcl: Please allow building with clisp on currently unsupported architectures

Sébastien Villemot <[email protected]>
Newsgroups gmane.linux.debian.devel.bugs.general,gmane.linux.debian.ports.alpha,gmane.linux.debian.ports.hppa,gmane.linux.debian.ports.mips,gmane.linux.debian.ports.powerpc
Organization Debian
Message-ID <[email protected]>
Hi,

Le mercredi 01 avril 2020 à 16:43 +0200, John Paul Adrian Glaubitz a écrit :
> On 3/16/20 1:16 AM, John Paul Adrian Glaubitz wrote:
> > 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.
> 
> Any chance we can get this implemented for the next upload?
> 
> FWIW, sbcl builds fine for me on mipsel if clang is used as the C compiler,
> I'll file a separate bug report for that.

I have mixed feelings about this. I am worried by the fact that those
architectures are not really supported upstream. Hence, if by chance we
manage to compile SBCL on one of those mostly-unsupported archs, I
don’t know how we would be able to deal with regressions that could
appear in the future, and that would block testing migration for
supported archs.

What’s your view on this?

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  https://www.debian.org
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl6EqoMACgkQLOzpNQ7O
vkrEug/7BqpeAfiMIAvxj9H/d70wbynuY4EzuwVqH8tQWwEyyW5ymTXCgp7/e75u
MvyunTbk046sA/72Vf7Me7aYUOy5q0iznKGb5vno81XcMhUXG8EXoychj6E3clWP
V0jFpZuDBOYrK2zO7j1Ixh27XsZILhwfyuiZHWfrQWDIEK8edGeC2O27UN1Y950g
k9/3J9s2mmEp211+MNLwAIATdADmcxKH2GejnPRZPSuGpzrRfMT+a78OJciC8MiE
imknuw6WDvNED/EV8D9L9fAS0B4xG7sLrasjhysTN2yWL4Q7xlikyRf0b4Gv+rwI
mX6YEKYYBFxYREgjV1LsWp8MpYGn2s+wejvBAEjSx475ezEW0KU7GwGwJ7mo51oV
2rDstIuD/zfVfIyvNP6Pq4d7ERFvQ4xM5aXF8gGBLEeWZmPs0zZxPTUwysIDh/p+
gpRMuucDmLN5N04kj0laAafDFDpVNxcc4ENk/vdkGDq7rvI0KIcf/MKHdr1Ntyxr
EJZMPkN+uO3b3HEkLtZ9HXG0hP5IBnKr6pgMxxDOGTOKtOngY9/Q6FdqzvSg5Emj
qz+0qIUrxuU0gS/0CY4px7Ef55usrauQjBeXqE1m04ErdQp8/Sz4InCm+R9QJoRX
2OsO/7EPHymTLlL1i4ENdhVj6uJKNaIHOzTOhFg2zagz6YhkYHg=
=x4Yz
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.