I have tried to install LispWorks Personal 4.3.0 on my Debian Woody
system, but there is a problem with the Motif library. When I run
LispWorks, I get the error:
Error during GUI startup:
Motif version string (·@(#)Motif Version 2.1.30") indicates invalid library version. Requires (("Lesstif" "2.1") ("Motif" "2.2")).
According to the information at LispWorks' site, it requires Lesstif
0.93.18 or higher, or Open Motif 2.2. On my Woody system I have both
Lesstif 0.93.18 (installed in /usr/lib/libXm.so.1.0.2) and Open Motif
2.1.30-5 (in /usr/X11R6/lib/libXm.so.2.1). So, at least the former
should work.
I have tried changing the file lib/4-3-0-0/config/use-motif-library in
the LispWorks distribution so that it only looks for Lesstif:
(:detect-version (("/usr/lib/libXm.so.1.0.2" :lesstif)))
:prefer-version :lesstif)
but LispWorks apparently ignores the setting and always tries to
access Open Motif, as the above error message shows.
Before I fiddle with Motif versions (I'm not sure whether Open Motif
2.2 binaries or later are available for my glibc) or system settings,
is there any way of convincing LispWorks to use the installed version
of Lesstif?
Paolo
--
Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film
Recommended Common Lisp libraries/tools (Google for info on each):
- ASDF/ASDF-INSTALL: system building/installation
- CL-PPCRE: regular expressions
- UFFI: Foreign Function Interface
In article <··············@plato.moon.paoloamoroso.it>, Paolo Amoroso wrote:
> I have tried to install LispWorks Personal 4.3.0 on my Debian Woody
> system, but there is a problem with the Motif library. When I run
> LispWorks, I get the error:
>
> Error during GUI startup:
> Motif version string (·@(#)Motif Version 2.1.30") indicates
> invalid library version. Requires (("Lesstif" "2.1") ("Motif"
> "2.2")).
>
> According to the information at LispWorks' site, it requires Lesstif
> 0.93.18 or higher, or Open Motif 2.2. On my Woody system I have
> both Lesstif 0.93.18 (installed in /usr/lib/libXm.so.1.0.2) and Open
> Motif 2.1.30-5 (in /usr/X11R6/lib/libXm.so.2.1). So, at least the
> former should work.
[snip]
> Before I fiddle with Motif versions (I'm not sure whether Open Motif
> 2.2 binaries or later are available for my glibc) or system settings,
> is there any way of convincing LispWorks to use the installed version
> of Lesstif?
For what it's worth, LispWorks Personal Edition 4.3.7 on Debian
stable+some testing+some unstable works for me, both with Lesstif and
Open Motif.
Installed Motif-like packages:
# apt-show-versions | grep -i -e lesstif -e motif
lesstif2/testing upgradeable from 1:0.93.94-2 to 1:0.93.94-4
lesstif-bin/stable uptodate 1:0.93.18-4
lesstif1/stable uptodate 1:0.93.18-4
libmotif3/unstable uptodate 2.2.3-1
Installed glibc/libc-related packages:
# apt-show-versions | grep -i -e glibc -e libc6 -e libc5
libstdc++2.9-glibc2.1/stable uptodate 2.91.66-4
libc6/testing upgradeable from 2.3.2.ds1-12 to 2.3.2.ds1-13
libstdc++2.10-glibc2.2/stable uptodate 1:2.95.4-11woody1
libc5/stable uptodate 5.4.46-12
libg++2.8.1.3-glibc2.2/stable uptodate 1:2.95.4-11woody1
libc6-dev/testing upgradeable from 2.3.2.ds1-12 to 2.3.2.ds1-13
glibc-doc/stable uptodate 2.2.5-11.5
It seems to work better with Open Motif than lesstif. With lesstif
I'd get odd Xt errors[1]; with Open Motif I don't.
Perhaps try
apt-get -t unstable install libmotif3
? If you're running an all-Woody system, this could result in a lot
of upgraded packages, of course. And you need to've configured
/etc/apt/sources.list with places to find 'unstable' packages, etc,
etc.
-- Larry
[1] Warning: (Xt Warning) XtRemoveGrab asked to remove a widget not on the list
Paolo Amoroso <·······@mclink.it> wrote in message news:<··············@plato.moon.paoloamoroso.it>...
(snip)
> I have tried changing the file lib/4-3-0-0/config/use-motif-library in
> the LispWorks distribution so that it only looks for Lesstif:
>
> (:detect-version (("/usr/lib/libXm.so.1.0.2" :lesstif)))
> :prefer-version :lesstif)
>
> but LispWorks apparently ignores the setting and always tries to
> access Open Motif, as the above error message shows.
>
(snip)
> Paolo
I had the same problem, tried the same solution. Maybe a LW bug?
Gave up on Debian entirely, though (for BSD - but haven't tried LW on BSD yet).
Cheers
Hy