install of shared libs depending on other shared libs broken

[Roman Kagan]

Hi,

trying to build a package with several shared libs (heimdal-0.4e) I've
found out that the install of shared libs linked to other yet
uninstalled shared libs is improperly handled by libtool-1.4.2, when
the destination directory is different from "rpath" argument at link
time, e.g. in buildroot'ed rpm builds.

Here's the stripped down case:

mkdir -p /tmp/{src,lib}
cd src
touch x.c y.c
libtool gcc -c x.c
libtool gcc -c y.c
libtool --mode=link gcc -o libx.la -rpath /usr/lib x.lo
libtool --mode=link gcc -o liby.la -rpath /usr/lib y.lo libx.la
libtool --mode=install install -c libx.la /tmp/lib
libtool --mode=install install -c liby.la /tmp/lib

The last command outputs:

libtool: install: warning: relinking `liby.la'
cd /tmp/src; /bin/sh /usr/bin/libtool --mode=relink gcc -o liby.la -rpath 
/usr/lib y.lo libx.la
gcc -shared  y.lo  -L/usr/lib -lx   -Wl,-soname -Wl,liby.so.0 -o 
.libs/liby.so.0.0.0
/usr/bin/ld: cannot find -lx
collect2: ld returned 1 exit status
libtool: install: error: relink `liby.la' with the above command before 
installing it
libtool: install: warning: remember to run `libtool --finish /usr/lib'

I've tried it on several platforms
(linux-2.4.9/glibc-2.2.3/gcc-3.0.1/binutils-2.11.2,
solaris-2.7/gcc-3.0.1/GNU binutils-2.11.2,
solaris-2.7/gcc-2.95.3/native binutils) always with the same result so
I suspect a bug in libtool.  I've failed to fix it, though (shell
scripts of more than 5k lines are too fragile :).

  Cheers,
        Roman.