From: Stan Pinte <stan.pinte@wanadoo.be>
To: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-gtk@sources.redhat.com,Ariel Rios <ariel@gnu.org>
Subject: Re: (gnome gtk) et al
Date: Wed, 07 May 2003 14:02:00 -0000 [thread overview]
Message-ID: <20030507154227.2778f673.stan.pinte@wanadoo.be> (raw)
In-Reply-To: <20030507144720.703b50f1.stan.pinte@wanadoo.be>
On Wed, 7 May 2003 14:47:20 +0200
Stan Pinte <stan.pinte@wanadoo.be> wrote:
>
> hello,
>
> I managed to compile gnome-guile, by fixing some typos in some Makefile.in, and here is what I get when trying an example:
>
> /opt/guile-exp/bin/guile --debug -s canvas-test.scm
>
> stan@pablo:~/src/guile/exp/gnome-guile/guile-gnome/examples 120 $ /opt/guile-exp/bin/guile -s canvas-test.scm
> ERROR: In procedure dynamic-func:
> ERROR: /opt/guile-exp//lib/libguile-ltdl.so.1: undefined symbol: gnome_init_guile_glue
> stan@pablo:~/src/guile/exp/gnome-guile/guile-gnome/examples 121 $
>
>
> (I enclosed debug output below)
>
> any clue? because strace tells me that the program has opened the library:
---------------+
A first clue is that gnome-guile, in the GNOME CVS, uses a slightly different gtk/dynlink.scm file, which relies on tk/dynlink-old.scm ....
(define-public (merge-compiled-code init-func libname)
(cond
(gtkconf-using-ltdl
(let* ((module (current-module))
(interface (module-public-interface module)))
;; make the new primitives visible from within the current module.
(module-use! module interface) ; XXX - is this safe?
(save-module-excursion
(lambda ()
(set-current-module interface)
(load-extension libname init-func)))))
(else
(merge-compiled-code-old init-func libname))))
the question are: what does gtkconf-using-ltdl means? should merge-compiled-code-old be re-integrated in the guile-gtk CVS?
thanks,
Stan.
next prev parent reply other threads:[~2003-05-07 14:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030407144511.GA1489@lark>
2003-04-07 19:57 ` Ariel Rios
2003-04-07 20:15 ` Andreas Rottmann
2003-04-08 10:34 ` Marius Vollmer
2003-04-08 14:56 ` Stan Pinte
2003-04-08 20:03 ` Andreas Rottmann
2003-04-08 21:33 ` David Pirotte
2003-04-11 4:48 ` Steve Tell
2003-04-11 10:00 ` Andreas Rottmann
2003-04-09 15:24 ` Stan Pinte
2003-04-10 17:05 ` Andreas Rottmann
2003-04-10 17:10 ` David Pirotte
2003-05-06 6:52 ` Stan Pinte
2003-05-06 15:33 ` Marius Vollmer
2003-05-06 15:45 ` Stan Pinte
2003-05-07 13:07 ` Stan Pinte
2003-05-07 14:02 ` Stan Pinte [this message]
2003-05-07 14:10 ` Marius Vollmer
2003-05-07 14:38 ` Stan Pinte
2003-05-07 15:17 ` Stan Pinte
2003-05-07 18:16 ` Marius Vollmer
2003-05-08 11:43 ` Stan Pinte
2003-05-12 14:18 ` Stan Pinte
[not found] ` <1052750737.26632.4.camel@tosca.elektra.com.mx>
2003-05-12 16:48 ` Stan Pinte
2003-05-14 9:17 ` Andy Wingo
2003-05-16 14:26 ` Andreas Rottmann
2003-05-20 20:08 ` Andreas Rottmann
2003-05-23 22:00 ` Kevin Ryde
2003-05-26 13:04 ` Andreas Rottmann
2003-06-23 14:14 ` Andy Wingo
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=20030507154227.2778f673.stan.pinte@wanadoo.be \
--to=stan.pinte@wanadoo.be \
--cc=ariel@gnu.org \
--cc=guile-gtk@sources.redhat.com \
--cc=marius.vollmer@uni-dortmund.de \
/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).