public inbox for
 help / color / mirror / Atom feed
From: Stephen Tell <>
To: Marius Vollmer <>
Cc: Guile-Gtk List <>
Subject: Re: guile-gtk without dlopen (HP-UX)
Date: Mon, 08 Nov 1999 19:08:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 8 Nov 1999, Marius Vollmer wrote:

> 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.

I got my program running by hacking a copy of gtk/dynlink.scm,
removing all of the dlopen stuff, and changing 
merge-compiled-code to call the procedures try-using-libtool-name
and link-dynamic-module (found in boot-9.scm) instead of
dlopen-libtool-library and 

> 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

Steve Tell | | | KF4ZPF
Research Associate, Microelectronic Systems Laboratory
Computer Science Department, UNC@Chapel Hill.   W:919-962-1845

  reply	other threads:[~1999-11-08 19:08 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
1999-11-08 19:08   ` Stephen Tell [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).