RSS/Atom feed Twitter
Site is read-only, email is disabled

Link glib

This discussion is connected to the gegl-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

3 of 3 messages available
Toggle history

Please log in to manage your subscriptions.

Link glib hce 16 Jan 09:22
  Link glib hce 16 Jan 10:22
   Link glib Martin Nordholts 17 Jan 12:35
hce
2010-01-16 09:22:01 UTC (about 15 years ago)

Link glib

Hi,

Sorry for asking an off topic question. While I was building gegl-0.1.0 on an old Debian 4.0 box with default glib version 2.12 on /usr/lib, it was an error for old glib version. I installed glib2.20 in a local directory and set it by pkg-config and ldconfig. I could not remove the glib2.12 as it The pkg-config and ldconfig now include both glib2.12 and glib2.20 and build gegl failed link as the glib2.12 took first. Has anyone

hce
2010-01-16 10:22:49 UTC (about 15 years ago)

Link glib

Sorry, my web mail crashed and sending a mess message. Let me try it again:

I could not build gegl-0.1.0 on Debian 4.0 with the glib version 2.12 in /usr/lib. So, I built glib2.20 in a local directory and set it up in pkg-config and ldconfig. But I could not remove /usr/lib/glib2.12 version as many dependant gnome applications would also be removed. It ended up with both versions of glib in pkg-config and ldcondig.

It was fine to run the gegl configure, it picked up glib2.20, but it failed in make although both glib2.12 in /usr/lib/libglib-2.0.so and glib2.20 were included in libtool link command:

../gegl/.libs/libgegl-0.0.so: undefined reference to `g_dgettext'

I checked Makefile and thought if I could remove glib2.12 /usr/lib path manually from GLIB_LIBS in Makefile it would ok, but the GLIB_LIBS does not include glib2.12, it actually only included glib2.20 path in the Makefile. Now I confused, if the /usr/lib/libglib-2.0.so is not in the Makefile, where the link /usr/lib/libglib-2.0.so came from? Please advice.

Alternatively, it might better to manually link glib2.20 in ldconfig, I know there is a command ldconfig -l, but I've never done it, if anyone knows how to do it, appreciate your help.

Thank you.

Kind Regards,

Jupiter

Martin Nordholts
2010-01-17 12:35:59 UTC (about 15 years ago)

Link glib

hce wrote:

I could not build gegl-0.1.0 on Debian 4.0 with the glib version 2.12 in /usr/lib. So, I built glib2.20 in a local directory and set it up in pkg-config and ldconfig. But I could not remove /usr/lib/glib2.12 version as many dependant gnome applications would also be removed. It ended up with both versions of glib in pkg-config and ldcondig.

It was fine to run the gegl configure, it picked up glib2.20, but it failed in make although both glib2.12 in /usr/lib/libglib-2.0.so and glib2.20 were included in libtool link command:

You don't need to manually bother with environment variables if you follow the advice here:
http://www.chromecode.com/2009/12/best-way-to-keep-up-with-gimp-from-git_26.html

You use the same prefix for both GLib and GEGL and the other dependencies you have

If libtool still refuses to link correctly you can try to remove (or better, move away) the *.la files in /usr/lib and $gegl_prefix/lib, iirc this sometimes fixes the weird problems.

Regards, Martin