Sebastian Tennant <[EMAIL PROTECTED]> writes:
> /usr/share/guile/1.8/ looks like this:
>
> /usr/share/guile/1.8:
> total used in directory 308 available 2752472
> drwxr-xr-x 7 root root 116 Mar 27 14:22 .
> drwxr-xr-x 3 root root 16 Feb 28 23:59 ..
> -rw-r--r-- 1 root root 291463 Mar 5 2007 guile-procedures.txt
> drwxr-xr-x 3 root root 4096 Mar 18 23:25 ice-9
> drwxr-xr-x 3 root root 18 Feb 28 23:59 lang
> drwxr-xr-x 3 root root 34 Feb 28 23:59 oop
> drwxr-xr-x 2 root root 4096 Mar 15 20:14 scripts
> lrwxrwxrwx 1 root root 15 Mar 18 23:01 slib -> /usr/share/slib
> -rw-r--r-- 1 root root 7818 Mar 27 14:22 slibcat
> drwxr-xr-x 2 root root 4096 Mar 18 21:59 srfi
I have since discovered that if the symbolic link is placed in
/usr/share/guile, and NOT a version directory then
(use-modules (ice-9 slib))
works as intended. (The catalog 'slibcat' _is_ created in the current
version directory).
The documentation reads:
2. Define the `SCHEME_LIBRARY_PATH' environment variable:
$ SCHEME_LIBRARY_PATH=/usr/local/lib/slib/
$ export SCHEME_LIBRARY_PATH
Alternatively, you can create a symlink in the Guile directory to
SLIB, e.g.:
ln -s /usr/local/lib/slib /usr/local/share/guile/1.8/slib
In my experience ONLY the symlink trick works, provided the
directory
/usr/share/guile
is used, and not a version directory, such as
/usr/share/guile/1.8
Setting SCHEME_LIBRARY_PATH doesn't seem to do anything.
Sebastian
