Re: How CLSQL finds and loads foreign libraries

On Wed, 6 Jul 2005 06:26:22 -0600, Kevin Rosenberg <kevin-HJRc7zDS/[email protected]> wrote:

> Are you sure this works for CMUCL? An test case illustrating
> http://bugs.debian.org/317097

Yes, I've tested this before I submitted the patch.  Here are the
results from my Debian system:

  edi@vmware:/tmp$ locate libz.so
  /usr/lib/libz.so
  /usr/lib/libz.so.1
  /usr/lib/libz.so.1.2.2
  /var/lib/postgres/dumpall/7.4/libz.so.1
  /var/lib/postgres/dumpall/7.4/libz.so.1.2.2
  edi@vmware:/tmp$ ls -l /usr/lib/libz.so
  lrwxrwxrwx  1 root root 9 May  4 22:33 /usr/lib/libz.so -> libz.so.1
  edi@vmware:/tmp$ pwd
  /tmp
  edi@vmware:/tmp$ ls *.so
  ls: *.so: No such file or directory
  edi@vmware:/tmp$ cmucl
  * (sys::load-object-file "libz.so")

  ((#.(SYSTEM:INT-SAP #x0806EB70) . "libz.so") (#.(SYSTEM:INT-SAP #x40016ED8)))
  * (lisp-implementation-version)

  "CVS pre1-19a 19b-pre1-20050606 + minimal debian patches (19B)"

I wonder what the difference between our system might be that causes
this - your newer CMUCL version maybe?  But why should they make such
a change?

Cheers,
Edi.