From: Jay Sulzberger <jays@panix.com>
To: guile-user@gnu.org
Subject: Re: How does one use SLIB with guile-2.0 on Debian?
Date: Sun, 25 Mar 2012 12:42:03 -0400 (EDT) [thread overview]
Message-ID: <Pine.NEB.4.64.1203250102100.14769@panix5.panix.com> (raw)
In-Reply-To: <Pine.NEB.4.64.1203221553570.12884@panix5.panix.com>
On Sat, 24 Mar 2012, Jay Sulzberger wrote:
> I am running a mainly "testing" version of Debian GNU/Linux, and
> here is the version of Guile I have installed via apt-get:
>
> guile (GNU Guile) 2.0.5-deb+1-1
>
> I would like to use SLIB with this guile.
>
> How do I do it?
>
> oo--JS.
Ah, I see there are some difficulties.
I installed slib-3b3. Guile and SLIB still do not work together
properly, but the errors are different, and doing
(use-modules (ice-9 slib))
at the repl does not result in errors reported at the repl.
I believe that it almost works and a few days effort would get me
a working Guile 2.0 and SLIB system.
oo--JS.
prev parent reply other threads:[~2012-03-25 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 22:42 How does one use SLIB with guile-2.0 on Debian? Jay Sulzberger
2012-03-25 16:42 ` Jay Sulzberger [this message]
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=Pine.NEB.4.64.1203250102100.14769@panix5.panix.com \
--to=jays@panix.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).