From: Alexey Rodriguez Y <alexey@memi.umss.edu.bo>
To: Marius Vollmer <mvo@zagadka.ping.de>, Bo Forslund <bo.forslund@abc.se>
Cc: guile-gtk list <guile-gtk@sourceware.cygnus.com>
Subject: Re: ERROR: In procedure dynamic-link:
Date: Thu, 18 Oct 2001 10:59:00 -0000 [thread overview]
Message-ID: <200111162220.fAGMKYq02198@orion.memi.umss.edu.bo> (raw)
In-Reply-To: <87pu6j4n9q.fsf@zagadka.ping.de>
The version of guile in mdk8.1 is 1.4. I found this in /usr/lib
/usr/lib/libltdl.so.3
is this a recent version?
When i straced guile when loading gtk it was looking for some .la files but
finally it looked for libfoo (without .so). I don't have access to the
machine right now, i can't provide the strace file.
On Thursday 15 November 2001 19:39, Marius Vollmer wrote:
> Bo Forslund <bo.forslund@abc.se> writes:
> > How is it with libnames?
>
> The function `dynamic-link' is supposed to supply the extension on its
> own. This is the reason you shouldn't specify any. For example,
> Guile will first look for a `libtool archive#' with extension ".la".
> Such an archive is a short description file that will then direct the
> actual loading of the real shared library. This might be necessary on
> platforms that don't support inter-library dependencies, or have funny
> versioning schemes. Also, not all platforms use ".so". HP/UX uses
> ".sl" I think, and Win32 uses ".dll". So it's better the let Guile
> choose the extension.
>
> This does not seem to work for you, however. What version of Guile
> are you using? Maybe we need to make sure that it includes the right
> version of libltdl (the lower level that handles all the dirty bits
> about dynamic linking).
>
> Libltdl has been known for producing "file not found" error messages
> for just about any kind of error. You can't, unfortunately, assume
> that the real cause is indeed some file not being found.
>
> This should have been fixed already, however, but it could be that the
> version of Guile that you are using has not yet picked up that fix.
>
> It might be helpful to use `strace' to find out what files guile or
> guile-gtk are really looking for and which are opened successfully.
>
> > So I did this in dynlink.scm
> >
> > (define string-append
>
> ( Why do you define string-append? There is a builtin string-append. )
>
> > Then at what used to be /usr/share/guile/gtk/dynlink.scm:19:34:
> > (dynamic-call init-func (dynamic-link (string-append libname ".so")))
> >
> > Not very elegant but it works.
>
> Which is kinda strange.
>
> It _could_ be that you have a very old version of Guile that doesn't
> provide its own extensions lib shared libraries. That would have to
> be Guile 1.3.4 or something.
next prev parent reply other threads:[~2001-11-16 22:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 4:34 Bo Forslund
2001-10-11 6:16 ` Alexey Rodriguez Y
2001-10-11 13:25 ` Bo Forslund
2001-10-11 15:20 ` Alexey Rodriguez Y
2001-10-18 0:23 ` Bo Forslund
2001-10-18 3:10 ` Marius Vollmer
2001-10-18 10:59 ` Alexey Rodriguez Y [this message]
2001-10-19 15:01 ` Bo Forslund
2001-11-05 17:33 ` Marius Vollmer
2001-11-12 13:11 ` Bo Forslund
2001-11-14 10:53 ` Marius Vollmer
2001-11-12 14:08 ` Marius Vollmer
2001-11-14 20:24 ` Alexey Rodriguez Y
2001-11-15 5:28 ` Marius Vollmer
2001-11-15 7:11 ` Bo Forslund
2001-11-15 15:20 ` guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:) Steve Tell
2001-11-15 15:39 ` Steve Tell
2001-11-16 14:11 ` Bo Forslund
2001-11-17 6:17 ` Bo Forslund
2001-11-18 8:30 ` Yet a new version " Bo Forslund
2001-12-28 20:21 ` Bo Forslund
2001-12-28 17:07 ` guile-gtk snapshot " Bo Forslund
2001-12-28 16:47 ` Bo Forslund
2001-12-28 6:25 ` Steve Tell
2001-11-25 5:33 ` Ariel Rios
2001-12-30 23:39 ` Ariel Rios
2001-12-27 20:28 ` Steve Tell
2001-11-25 7:33 ` ERROR: In procedure dynamic-link: Bo Forslund
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200111162220.fAGMKYq02198@orion.memi.umss.edu.bo \
--to=alexey@memi.umss.edu.bo \
--cc=bo.forslund@abc.se \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=mvo@zagadka.ping.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).