On Tue, 19 Jun 2001, David Odin wrote:
> Indeed, there's something very... peculiar here:
> [dindinx@ke gobject]$ pwd
> /home/dindinx/RPM/BUILD/glib-1.3.6/gobject
> [dindinx@ke gobject]$ ldd .libs/gobject-query
> libgobject-1.3.so.6 => /usr/lib/libgobject-1.3.so.6 (0x4002d000)
> libglib-1.3.so.6 => /usr/lib/libglib-1.3.so.6 (0x40063000)
> libc.so.6 => /lib/libc.so.6 (0x400bd000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> libglib-1.3.so.5 => not found
> [dindinx@ke gobject]$ ldd .libs/glib-genmarshal
> libglib-1.3.so.6 => /usr/lib/libglib-1.3.so.6 (0x4002d000)
> libc.so.6 => /lib/libc.so.6 (0x40087000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
This seems to tell just that you have installed the non-working libglib
package, where libgobject-1.3.so.6 links against libglib-1.3.so.5
AFAICS, the binaries are always linked correctly, the problem are
the libraries libgobject, libgmodule and libgthread, so the reference
to libglib-1.3.so.5 is derived from libgobject.
> I cannot understand why glib-genmarshal isn't linked against libglib-1.3.so.5
> while gobject-query is. FYI:
> [dindinx@ke .libs]$ ldd libgobject-1.3.so.6.0.0
> libglib-1.3.so.6 =>
>/home/dindinx/RPM/BUILD/glib-1.3.6/.libs/libglib-1.3.so.6 (0x40037000)
> libc.so.6 => /lib/libc.so.6 (0x400a7000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)
>
After 'make install', you find another file called libgobject-1.3.so.6.0.0T
that is linked incorrectly and this one gets installed, See the .so-files
in $RPM_BUILD_ROOT/usr/lib.
The problem is definitely the relink-command variable in libg{object|
module|thread}-1.3.la. I just could not figure out exactly how it is
generated by libtool (lines 4090-4200).
Arnd <><
