unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Michael Vanier <mvanier@cs.caltech.edu>
Subject: guile can't find dynamically loaded library
Date: Mon, 30 Sep 2002 18:08:12 -0700	[thread overview]
Message-ID: <200210010108.g9118Cm11313@orchestra.cs.caltech.edu> (raw)


Hi,

I've been walking through the guile info documentation, specifically the
section on defining your own guile extensions.  This is for guile-1.6
running on a Debian GNU/Linux system.  I am unable to get guile to find the
location of the shared library that I created (libguile-bessel.so).  I have
tried everything I can think of.  I have put the file into /usr/lib and it
still couldn't find it!  I setenv'd LTDL_LIBRARY_PATH to the current
directory; no dice (is LTDL a misprint?).  I always get the following
message:

guile> (load-extension "libguile-bessel" "init_bessel")
standard input:1:1: In procedure dynamic-link in expression (load-extension "libguile-bessel" "init_bessel"):
standard input:1:1: file: "libguile-bessel", message: "file not found"
ABORT: (misc-error)

Type "(backtrace)" to get more information or "(debug)" to enter the debugger.
guile> 

I suspect that the documentation is incorrect.  Can you clarify what's
needed to inform guile of where a shared library is?

Mike





_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile


             reply	other threads:[~2002-10-01  1:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01  1:08 Michael Vanier [this message]
2002-10-03 18:34 ` guile can't find dynamically loaded library Marius Vollmer
2002-10-05  6:05   ` Michael Vanier
2002-10-05 18:35     ` Paul Jarc
2002-10-08 21:30     ` Marius Vollmer
2002-10-08 21:42       ` Michael Vanier
2002-10-08 22:40         ` Marius Vollmer

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=200210010108.g9118Cm11313@orchestra.cs.caltech.edu \
    --to=mvanier@cs.caltech.edu \
    /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).