From: Rob Browning <rlb@defaultvalue.org>
Cc: gary@gnu.org
Subject: Re: Dynamic loading problem
Date: Fri, 20 Dec 2002 16:12:26 -0600 [thread overview]
Message-ID: <87k7i4xrud.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <m3wun7csmu.fsf@lumo.pacujo.net> (Marko Rauhamaa's message of "20 Nov 2002 23:02:33 -0800")
Marko Rauhamaa <marko@pacujo.net> writes:
> Just installed libguile-1.6 and guile-gtk-1.2 on SuSE 7.3. Loading gtk
> failed. The reason is an inconsistency between ltdl.c and linux dlopen.
Technically this isn't a guile bug, it's the way libtool was designed
to work AFAIK, but we *are* planning to change it in libguile-ltdl.
This change may or may not ever make it into the guile 1.6 tree,
though. If not, it's definitely planned for 1.8.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2002-12-20 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 7:02 Dynamic loading problem Marko Rauhamaa
2002-12-20 22:12 ` 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=87k7i4xrud.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=gary@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).