From: Rob Browning <rlb@defaultvalue.org>
Cc: Bill Gribble <grib@linuxdevel.com>,
Martin Grabmueller <mgrabmue@cs.tu-berlin.de>,
guile-user@gnu.org
Subject: Re: dynamic-link and LD_LIBRARY_PATH
Date: Wed, 10 Apr 2002 15:10:49 -0500 [thread overview]
Message-ID: <877knfwbzq.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <1008617386.16363.1.camel@alienway> ("Anthony W. Juckel"'s message of "17 Dec 2001 13:29:45 -0600")
"Anthony W. Juckel" <awj@digitalgreen.com> writes:
>> If you force a .so file to be opened, you must have already dlopened any
>> other shared libs that the .so needs symbols from or you will see a
>> "File not found" error.
>
> This does indeed seem to be the case. Thank you very much.
The upcoming 1.6 has the error message fixed to give a better
indication of what guile was looking for when the link failed.
However, there's no way to get more precise info about exactly what
went wrong, without a redesign of the libtool ltdl interface to allow
it to return more than just a static error string.
Another thing that people should watch out for is that older
libtool/guile combinations were ok with (dynamic-link "libfoo.so"),
but this won't work anymore -- in most cases, you just need to change
the call to omit the extension (as Bill suggested), i.e. (dynamic-link
"libfoo").
Hope this helps.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-04-10 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C1D7000.7070403@digitalgreen.com>
[not found] ` <200112170953.fBH9rJs23122@pepita.cs.tu-berlin.de>
[not found] ` <3C1E1CE0.2060202@digitalgreen.com>
2002-04-02 13:57 ` dynamic-link and LD_LIBRARY_PATH Bill Gribble
[not found] ` <1008617386.16363.1.camel@alienway>
2002-04-02 13:57 ` Bill Gribble
2002-04-10 20:10 ` Rob Browning [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=877knfwbzq.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=grib@linuxdevel.com \
--cc=guile-user@gnu.org \
--cc=mgrabmue@cs.tu-berlin.de \
/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).