From: | Michael Orlitzky <mjo@g.o> | ||
---|---|---|---|
To: | gentoo-dev@l.g.o | ||
Subject: | Re: [gentoo-dev] musl, sbcl, and ros | ||
Date: | Sat, 03 Dec 2022 02:46:24 | ||
Message-Id: | 14605b6854f84d53d4fbc0a1b1613cd60afb92ca.camel@gentoo.org | ||
In Reply to: | Re: [gentoo-dev] musl, sbcl, and ros by "Haelwenn (lanodan) Monnier" |
1 | On Sat, 2022-12-03 at 02:59 +0100, Haelwenn (lanodan) Monnier wrote: |
2 | > [2022-12-02 05:11:15+0000] Andrey Grozin: |
3 | > > In principle, one can try a workaround: use some other lisp (say, clisp or |
4 | > > ecl) as the bootstrap lisp. This way is at best brittle: there is no |
5 | > > guarantee that these external lisps will compile the sbcl sources |
6 | > > successfully. People say that sometimes this works. |
7 | > |
8 | > Well Alpine is using the ecl route: https://git.alpinelinux.org/aports/tree/community/sbcl/APKBUILD |
9 | |
10 | ECL is a good choice. Upstream is active and friendly..... but: |
11 | |
12 | The current and only version of ECL in the tree has a bug that makes it |
13 | unusable for compiling SBCL: |
14 | |
15 | * https://bugs.launchpad.net/sbcl/+bug/1956852 |
16 | * https://gitlab.com/embeddable-common-lisp/ecl/-/issues/667 |
17 | |
18 | A fix was committed, but there hasn't been a new release yet. |