Mark Crichton wrote:
* Steve M. Robbins (steven.robbins@videotron.ca) [020324 14:01]:Hello Eric, I'm sorry for the breakage. I've come up with a workaround that I will upload later today, but I'm a bit puzzled about the problem, so I thought I'd see if the python-gdk-imlib, libglib1.2 maintainer, or any of the gtk/gnome crowd knows the score.Ok, that bug is out of my league. Talk to james@daa.com.au. He's the GTK Python binding guru. He might know the answer. For a laugh, try removing -module from the Makefile's in gdk_imlib, recompile and see if it works. I had to add it for people who wanted Darwin support for some reason (it appeared to be a libtool bug). Oh, I just remembered! Check to see if your modules depend on libgdk-imlib using ldd. If they don't, I think that could be a problem.
Hmm. The Makefile.am looks a bit weird in the gdk_imlib directory.You should just list the .la file on the _LIBADD line for each of the loader modules, rather than .libs/libgdk_imlib.so. Libtool will take care of linking things correctly. When writing Makefile.am's, you should ignore the .libs directory.
Adding -module to $(common_ldflags) is also correct. Some platforms need libraries to be linked in a special way if they are going to be dlopen'd, and that flag is used to tell libtool that you plan to do it (on linux, it doesn't really do anything other than letting you create libraries that don't start with "lib").
James. -- Email: james@daa.com.au WWW: http://www.daa.com.au/~james/ -- To UNSUBSCRIBE, email to debian-gtk-gnome-request@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org