This is the mail archive of the
cygwin
mailing list for the Cygwin project.
cygwin-1.7/clisp-2.48-1: Cannot initialize clisp with full linking set
- From: Mark Harig <idirectscm at aim dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Sun, 09 Aug 2009 16:24:59 -0400
- Subject: cygwin-1.7/clisp-2.48-1: Cannot initialize clisp with full linking set
Thank you for providing clisp version 2.48.
I am unable to start clisp if I specify the full linking set:
$ clisp -Kfull
/usr/lib/clisp-2.48/full/lisp.exe: error while loading shared libraries:
svm.dll: cannot open shared object file: No such file or directory
$ cygcheck -l clisp | grep svm.dll
/usr/lib/clisp-2.48/full/svm.dll
$ file /usr/lib/clisp-2.48/full/svm.dll
/usr/lib/clisp-2.48/full/svm.dll: PE32 executable for MS Windows (DLL)
(console) Intel 80386 32-bit
$ md5sum /usr/lib/clisp-2.48/full/svm.dll
3f0dfd94d955bfb567581c853ed32587 */usr/lib/clisp-2.48/full/svm.dll
$ cygcheck -c clisp
Cygwin Package Information
Package Version Status
clisp 2.48-1 OK
/usr/lib/clisp-2.48/full/svm.dll was installed with the executable
permission turned off. Turning on the executable permission had no effect:
$ chmod +x /usr/lib/clisp-2.48/full/svm.dll
$ ls -l /usr/lib/clisp-2.48/full/svm.dll
-rwxr-xr-x 1 username root 99K Aug 1 16:02
/usr/lib/clisp-2.48/full/svm.dll*
$ clisp -Kfull
/usr/lib/clisp-2.48/full/lisp.exe: error while loading shared libraries:
svm.dll: cannot open shared object file: No such file or directory
Also, the following (possibly related?) problem exists:
$ cd /usr/lib/clisp-2.48/full
$ clisp -Kfull
/usr/lib/clisp-2.48/full/lisp.exe: error while loading shared libraries:
cygdb-4.6.dll: cannot open shared object file: No such file or directory
There is no version cygdb-4.6.dll installed, and, as far as I can tell,
there is no version cygdb-4.6.dll available yet.
If the base linking set is specified, then clisp starts and exits
without error:
$ clisp -Kbase -q
[1]> (exit)
$
Can anyone suggest any troubleshooting steps to take to resolve this
problem,
or are these problems above caused by errors in the Cygwin packaging of
clisp?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple