Libtool warning: library seems to be moved.

[Peter Hyman]

gcc=3.3.4
libtool=1.5.6
autoconf=2.59
automake=1.8.5
os=Slackware 10.0
Kernel=2.6.7

When compiling programs (evolution 1.5.90 here), linker returns warning
when compiling such as:

/bin/sh ../../libtool --mode=link gcc  -g -O2 -Wall -Wmissing-prototypes  
-Wno-sign-compare 
-o libeabutil.la   eab-marshal.lo e-destination.lo eab-book-util.lo 
../../camel/libcamel.la ../../e-util/libeutil.la 
libtool: link: warning: 
`/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../..//libgal-2.2.la' seems to 
be moved
libtool: link: warning: 
`/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../..//libgthread-2.0.la' seems 
to be moved
libtool: link: warning: 
`/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../..//libgal-2.2.la' seems to 
be moved

The relevant .la file shows the following.

# Libraries that this one depends upon.
dependency_libs=' /mnt/src/evolution/camel/libcamel.la -L/usr/X11R6/lib 
-L/usr/lib/mozilla-1.7 
-L/usr/lib 
/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../..//libgthread-2.0.la 
/usr/lib/libgal-2.2.la 
-lnss3 -lsmime3 -lssl3 -lsoftokn3 /mnt/src/evolution/e-util/libeutil.la 
/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../..//libgal-2.2.la 
/usr/lib/libgal-a11y-2.2.la 
/usr/lib/libgnomeprintui-2-2.la /usr/lib/libglade-2.0.la 
/usr/lib/libgnomeprint-2-2.la 

While the needed libraries are in place, this causes make install to
attempt to compile all modules that did not link again. This is not a
showstopper, but a time waster!

At first, I thought the double backslash was the problem, so I changed
libtool.m4 as follows:

1099: sys_lib_search_path_spec=`$CC -print-search-dirs | grep "^libraries:" | 
$SED -e "s/^libraries://" -e "s,=/,/,g" -e "s,/:,:,g" -e "s,/$,,"`

This will remove trailing /'s and replace them with separators or at the
end of the line, with nothing.

The location of the libraries are all /usr/lib, so I am unclear why the
extremely log relative path to the libraries are shown sometimes, and
not others!.

However, the problem persists, and I do not see why. This may or may not
be a bug -- it could be a mis-compilation on Slackware's part of some
core library (although I built gal myself). However, this is a new
problem that I did not notice before using gcc 3.2.3, autoconf 2.59 and
automake 1.7.7.

Good Luck!
-- 
Peter Hyman