Bug#344912: tetex-bin: binaries linked against unneeded libraries

[Frank Küster <frank@kuesterei.ch>]

Frank Küster <frank@debian.org> wrote:

> I don't know how this is happening, but this line looks suspcicious:
>
> -gcc -shared [long list of .lo files] -Wl,-soname -Wl,libkpathsea.so.4 -o ../kpathsea/.libs/libkpathsea.so.4.0.0
> +gcc -shared [long list of .lo files] -L/usr/X11R6/lib -L/usr/lib /usr/lib/libpoppler.so -Wl,-soname -Wl,libkpathsea.so.4 -o ../kpathsea/.libs/libkpathsea.so.4.0.0

Indeed - trying that manually shows that for the first line, we get

$ ldd libkpathsea.so.4.0.0 
		libc.so.6 => /lib/tls/libc.so.6 (0xb7ea7000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

The same result with 

gcc -shared $lofiles -L/usr/X11R6/lib -L/usr/lib -Wl,-soname -Wl,libkpathsea.so.4 -o libkpathsea.so.4.0.0

So it's really the "/usr/lib/libpoppler.so" that makes the difference.

> why is there this "/usr/lib/libpoppler.so"?  Of course, libtool
> invocation two lines earlier changed:
>
> -/bin/sh ../libtool --mode=link gcc -o ../kpathsea/libkpathsea.la -rpath /usr/lib -version-info 4:0:0 [long list of .lo files]
> +/bin/sh ../libtool --mode=link gcc -o ../kpathsea/libkpathsea.la -lpoppler  -rpath /usr/lib -version-info 4:0:0 [long list of .lo files]
>
[...]
> But why does libtool pass "/usr/lib/libpoppler.so"?

I still don't know.  Well, I found the place after calling libtool with
sh -x, but I don't understand it.

Regards, Frank
-- 
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer