From Newsgroup: alt.os.linux.slackware
Henrik Carlqvist <
Henrik.Carlqvist@deadspam.com> writes:
...
been using snapshots of the unreleased 2.50 version. I don't run
current, myself, and my Lisp usage is so rudimentary that the version
likely wouldn't matter at all. Still, I'm curious if anyone knows the
background for this change. 2.49 does date back to 2010, but I see other
projects sticking with that.
Looking at the ChangeLog when clisp 2.50 was introduced would make me
guess that upgrading to that "beta" version was needed to support a new version of libunistring:
...
d/clisp-2.50_20220927_acb1266ee-x86_64-1.txz: Upgraded.
Compiled against libunistring-1.1.
...
However, the libunistring explanation is only a guess from my side, maybe version 2.49 would also work with the new libunistring and the upgrade to 2.50 was a mistake?
Seems reasonable.
I missed that Debian unstable actually also is taking versions from
upstream's git repo. It's confusing, as Slackware and Debian are using
quite different version number schemes while perhaps taking similar
code, give or take some months:
Slackware current:
Wed Jun 11 22:22:57 UTC 2025
d/clisp-2.50_20250504_f66220939-x86_64-1.txz: Upgraded.
Debian unstable:
Version: 1:2.49.20241228.gitc3ec11b-2
http://deb.debian.org/debian/pool/main/c/clisp/clisp_2.49.20241228.gitc3ec11b-2.dsc
They are in the same branch, I think. If you look in src/version.h in
f66220939 upstream it shows a version with 2.49 in its string, at least
for now, which maybe is why debian included 2.49 in their package version:
#define PACKAGE_VERSION "2.49.95+ (2024-11-03)"
https://gitlab.com/gnu-clisp/clisp/-/blob/master/src/version.h?ref_type=heads
NetBSD/pkgsrc still has 2.49 from 2010, not a repo snapshot, as does
Beyond Linux from Scratch. It looks to me like both of them opt not to
link to libunistring, that being an optional dependency. BLfS does link
to libunistring in their guile instructions. pkgsrc's lack of linkage I
show below. So that supports your guess. Maybe they intentionally
avoided it after having problems. pkgsrc libunistring is at version 1.2
now, even newer (and more problematic for clisp 2.49?) than the 1.1
version in the older Slackware current changelog you cited.
% ldd /usr/pkg/lib/clisp/base/lisp.run
/usr/pkg/lib/clisp/base/lisp.run:
-lreadline.8 => /usr/pkg/lib/libreadline.so.8
-lterminfo.2 => /usr/lib/libterminfo.so.2
-lc.12 => /usr/lib/libc.so.12
-lm.0 => /usr/lib/libm.so.0
-lcrypt.1 => /usr/lib/libcrypt.so.1
-lintl.1 => /usr/lib/libintl.so.1
-lavcall.1 => /usr/pkg/lib/libavcall.so.1
-lcallback.1 => /usr/pkg/lib/libcallback.so.1
-lpthread.1 => /usr/lib/libpthread.so.1
-lsigsegv.2 => /usr/pkg/lib/libsigsegv.so.2
Funny, I just noticed I had a newer, git based clisp compiled outside
pkgsrc on NetBSD, myself. I'd forgotten, but it looked like I was
getting segmentation faults from swank when trying to run slime. But I
was taking a git slime, so maybe I was mixing new wine with old
wineskins. I wonder if anyone on slackware hit anything like this with
2.49 or if I just made bad decisions when installing slime on
NetBSD. I'll have to try slime again on Slackware 15.0 with clisp 2.49.
Oh, also interesting, is this clisp (pkgsrc/NetBSD) without libunistring
linked still shows :UNICODE among its features. Skimming the surface of
this I remain puzzled:
*features*
(:READLINE :REGEXP :SYSCALLS :I18N :LOOP :COMPILER :CLOS :MOP :CLISP :ANSI-CL
:COMMON-LISP :LISP=CL :INTERPRETER :SOCKETS :GENERIC-STREAMS
:LOGICAL-PATHNAMES :SCREEN :FFI :GETTEXT :UNICODE :BASE-CHAR=CHARACTER
:WORD-SIZE=64 :PC386 :UNIX)
Regards,
Mike Sm.
--- Synchronet 3.21d-Linux NewsLink 1.2