From: Sebastian Tennant <sebyte@smolny.plus.com>
To: guile-user@gnu.org
Subject: Re: SLIB and ice-9 slib module
Date: Sun, 30 Mar 2008 16:06:39 +0000 [thread overview]
Message-ID: <7ifkmc1c.fsf@vps203.linuxvps.org> (raw)
In-Reply-To: 4pas6wxn.fsf@vps203.linuxvps.org
Sebastian Tennant <sebyte@smolny.plus.com> 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
next prev parent reply other threads:[~2008-03-30 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 23:30 SLIB and ice-9 slib module Sebastian Tennant
2008-03-27 8:26 ` Ludovic Courtès
2008-03-27 14:52 ` Sebastian Tennant
2008-03-30 16:06 ` Sebastian Tennant [this message]
2008-03-30 16:34 ` Ludovic Courtès
2008-03-30 17:54 ` Sebastian Tennant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ifkmc1c.fsf@vps203.linuxvps.org \
--to=sebyte@smolny.plus.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).