From: Marius Vollmer <mvo@zagadka.ping.de>
To: Daniel Skarda <0rfelyus@atrey.karlin.mff.cuni.cz>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: sgtk_dlopen
Date: Thu, 07 Oct 1999 13:11:00 -0000 [thread overview]
Message-ID: <87hfk3j7m9.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m07ll0d02f.fsf@atrey.karlin.mff.cuni.cz>
Daniel Skarda <0rfelyus@atrey.karlin.mff.cuni.cz> writes:
> Do you think that change `name' -=> `fullname' would break
> something?
I'm not sure, but I don't expect any breakage. I'm pretty agnostic
about dynamic linking issues right now. Does it help to have a
different LD_LIBRARY_PATH when running your unstable version?
> ps: what do you think about libltdl which comes with new version of
> libtool?
Definitely worth a look, but I rather put it into libguile and do away
with the dynlinking hacks of guile-gtk completely. I even have a
patch for libguile by one of the libltdl authors...
Yeah, I think I have to do something about this mess. I'll wait until
after guile-gtk-0.17, tho.
- Marius
prev parent reply other threads:[~1999-10-07 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-06 7:40 sgtk_dlopen Daniel Skarda
1999-10-07 13:11 ` Marius Vollmer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hfk3j7m9.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=0rfelyus@atrey.karlin.mff.cuni.cz \
--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).