From: Marius Vollmer <mvo@zagadka.ping.de>
To: Alexey Rodriguez Y <alexey@memi.umss.edu.bo>
Cc: Bo Forslund <bo.forslund@abc.se>,
guile-gtk list <guile-gtk@sourceware.cygnus.com>
Subject: Re: ERROR: In procedure dynamic-link:
Date: Thu, 15 Nov 2001 05:28:00 -0000 [thread overview]
Message-ID: <87667zht4y.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200111212059.fALKxcD08942@orion.memi.umss.edu.bo>
Alexey Rodriguez Y <alexey@memi.umss.edu.bo> writes:
> I am sending the output of strace when i run guile-gtk.
Ahh, so you are running guile-gtk, as opposed to just guile. Sorry, I
didn't noticed that earlier.
With guile-gtk, no dynamic loading of libguilegtk-1.2 should happen.
That is (was) the point of guile-gtk: it should work on systems where
dynamic linking would not.
From your strace output:
open("i686/mmx/libguilegtk-1.2.so.0", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("i686/libguilegtk-1.2.so.0", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("mmx/libguilegtk-1.2.so.0", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("libguilegtk-1.2.so.0", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=78514, ...}) = 0
old_mmap(NULL, 78514, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40017000
close(3) = 0
open("/usr/lib/libguilegtk-1.2.so.0", O_RDONLY) = 3
This shows what the OS is doing when starting guile-gtk, "main" has
not yet been called. You can see that is checks various locations
(probably from your LD_LIBRARY_PATH, right?) and then goes on to consult
/etc/ld.so.cache to find libguilegtk-1.2.so.0 in /usr/lib.
Later:
open("/users/alexey/proyecto/cint/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("i686/mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("i686/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 5
fstat64(5, {st_mode=S_IFREG|0644, st_size=78514, ...}) = 0
old_mmap(NULL, 78514, PROT_READ, MAP_PRIVATE, 5, 0) = 0x406ae000
close(5) = 0
open("/lib/i686/mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64("/lib/i686/mmx", 0xbfffe640) = -1 ENOENT
(No such file or directory)
open("/lib/i686/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64("/lib/i686", 0xbfffe640) = -1 ENOENT
(No such file or directory)
open("/lib/mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64("/lib/mmx", 0xbfffe640) = -1 ENOENT
(No such file or directory)
open("/lib/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64("/lib", {st_mode=S_IFDIR|0755, st_size=4864, ...}) = 0
open("/usr/lib/i686/mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64("/usr/lib/i686/mmx", 0xbfffe640) = -1 ENOENT
(No such file or directory)
open("/usr/lib/i686/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64("/usr/lib/i686", 0xbfffe640) = -1 ENOENT
(No such file or directory)
open("/usr/lib/mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64("/usr/lib/mmx", 0xbfffe640) = -1 ENOENT
(No such file or directory)
open("/usr/lib/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64("/usr/lib", {st_mode=S_IFDIR|0755, st_size=62712, ...}) = 0
munmap(0x406ae000, 78514) = 0
open("libguilegtk-1.2.la", O_RDONLY) = -1 ENOENT
(No such file or directory)
write(2, "ERROR", 5) = 5
write(2, ": ", 2) = 2
write(2, "In procedure ", 13) = 13
write(2, "dynamic-link", 12) = 12
write(2, ":\n", 2) = 2
write(2, "ERROR", 5) = 5
write(2, ": ", 2) = 2
write(2, "file not found", 14) = 14
write(2, "\n", 1) = 1
This looks very strange indeed, and does not fit with what I would
expect from the dynamic linking code in guile-1.4. The log above does
show no searching for a ".la" file, and no attempt at an ".so" file at
all.
I'm confused now. I think it would be best if you remove the Mandrake
guile packages from your system and install guile-1.5 from source. Bo
Forslund can help you with that, I think.
next prev parent reply other threads:[~2001-11-25 13:33 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
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 [this message]
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=87667zht4y.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=alexey@memi.umss.edu.bo \
--cc=bo.forslund@abc.se \
--cc=guile-gtk@sourceware.cygnus.com \
/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).