[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Neat gtk/gdk-imlib pain

Jason Gunthorpe <jgg@ualberta.ca> writes:

> This is kinda neat, considering what we were talking about with libtool
> and all, examine this ldd output:
> Wakko{jgg}~/work/apt#ldd `which wmakerconf `
>         libgdk_imlib.so.1 => /usr/lib/libgdk_imlib.so.1 (0x4000f000)
>         libgtk.so.1 => /usr/lib/libgtk.so.1 (0x40031000)
>         libgdk.so.1 => /usr/lib/libgdk.so.1 (0x400b3000)
>         libglib.so.1 => /usr/lib/libglib.so.1 (0x400cf000)
>         libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x400da000)
>         libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x400e2000)
>         libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x400ee000)
>         libm.so.6 => /lib/libm.so.6 (0x40191000)
>         libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x401aa000)
>         libtiff.so.3 => /usr/lib/libtiff.so.3 (0x401d4000)
>         libgif.so.3 => /usr/lib/libgif.so.3 (0x4020a000)
>         libpng.so.2 => /usr/lib/libpng.so.2 (0x40211000)
>         libz.so.1 => /usr/lib/libz.so.1 (0x4023e000)
>         libPropList.so.0 => /usr/lib/libPropList.so.0 (0x4024d000)
>         libnsl.so.1 => /lib/libnsl.so.1 (0x40258000)
>         libc.so.6 => /lib/libc.so.6 (0x4025e000)
>         libgmodule-1.1.so.13 => /usr/lib/libgmodule-1.1.so.13 (0x40303000)
>         libglib-1.1.so.13 => /usr/lib/libglib-1.1.so.13 (0x40306000)
>         libdl.so.2 => /lib/libdl.so.2 (0x40328000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> And note that it links to libglib twice. Turns out this is because there
> is two 'gdk-imlib1' packages with the same soname but linked against
> different versions of glib! By my count we have 72 different package that
> depend on gdk-imlib1..

I made the same mistable on my first cut of the Gnome packages.  It's important that
the higher level dependencies (ie. Gnome, WindowMaker, Enlightenment) use the exact
same libraries when building as the libraries they depend upon (ie. imlib, gtk, glib,
libjpeg, giflib, libtiff, etc.).

Does anybody have an idea about how to devise a lintian check for this
problem?  I can think of some crude solutions, but nothing really clean.
> I somehow sense that slink/potato gtk/gnome is going to be painfull..

I agree.  I'm only planning to support Gnome 0.99.x/1.0 on potato.


 - Jim

Reply to: