>From your description, it seems like there's a SBCL 2.3.7 somewhere in the system path. Running `whereis sbcl` should list out all available locations.
The other thing that has bitten me in the past is having an errant `SBCL_HOME` variable set in my environment, pointing to the wrong sbcl install directory. Anyway, hope you're able to isolate the issue - I can imagine it must be frustrating not being able to slime/sly connect to stumpwm. Good luck. On Wed, Oct 16, 2024 at 12:15 AM mintz--- via <stumpwm-devel@nongnu.org> wrote: > No, this error is not reproduced in SBCL. The file is compiled by the > correct version of SBCL, which is why I thought that SBCL version could be > hardcoded somewhere in Stumpwm. It doesn't seem to be the case, of course. > Apparently, I'm struggling with my own absentmindedness and the problem is > mine. Sorry. > > > 11 Oct 2024, 22:42 by s...@posteo.net: > > When I enable Swank in config, I get a strange message, saying that > file /usr/lib/sbcl/contrib/sb-cltl2.fasl "is a fasl file compiled with > SBCL 2.4.7.debian, and can't be loaded into SBCL 2.3.7.debian". > > > If you run SBCL in the terminal and try to quickload SWANK or SLYNK (or > just require sb-cltl2) do you get a similar error? > > If you do get the same error could you try removing SBCL from your > system (and ensuring the files are gone) and then reinstalling it? On my > system (void linux) the file `/usr/lib/sbcl/contrib/sb-cltl2.fasl` is > provided by the package `sbcl`. I'm unfamiliar with debian, but can you > use the package manager to find out what package provides that file and > see if it its version matches up with everything else? > > --szos > >
