From: Marius Vollmer <mvo@zagadka.ping.de>
To: Stephen Tell <tell@cs.unc.edu>
Cc: Guile-Gtk List <guile-gtk@sourceware.cygnus.com>
Subject: Re: guile-gtk without dlopen (HP-UX)
Date: Mon, 08 Nov 1999 13:27:00 -0000 [thread overview]
Message-ID: <87n1soptb1.fsf@zagadka.ping.de> (raw)
In-Reply-To: <Pine.GHP.4.10.9911071717060.27875-100000@rukbat.cs.unc.edu>
Stephen Tell <tell@cs.unc.edu> writes:
> Things are fine on linux, but I'm having a great deal of trouble with
> libraries and linking on HP-UX 10.20. HP-UX is a unix with wierd dynamic
> linking; using a function called shl_load() instead of dlopen(), so of
> course libguiledlopenhelper is going to lose.
Yes, dynamic linking is weird with guile-gtk in general, and I'm sorry
you have to suffer.
However, in recent releases of Guile, dynamic-link uses RTLD_GLOBAL by
default and thus libguiledlopenhelper is not needed at all (on dlopen
platforms). You might have to check the HPUX support of Guile if it
behaves correctly, tho. You could try to hack gtk/dynlink.scm so that
it doesn't use the %sgtk-* functions at all. If this doesn't work, we
can then see how you can get by without dynamic linking.
For the real fix, I think we need to have configure find out whether
libguiledlopenhelper is needed or not because people might still be
using old versions of Guile.
> guile-1.3.4
This is recent enough.
- Marius
next prev parent reply other threads:[~1999-11-08 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-07 15:47 Stephen Tell
1999-11-08 13:27 ` Marius Vollmer [this message]
1999-11-08 19:08 ` Stephen Tell
1999-11-18 13:05 ` Converting GdkEvent from C to Guile Stephen Tell
1999-11-18 15:14 ` Marius Vollmer
1999-11-18 15:50 ` Stephen Tell
1999-11-19 13:51 ` Marius Vollmer
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=87n1soptb1.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=tell@cs.unc.edu \
/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).