I've the same problem when compiling Mono and pangopdf...
Could the problem be related to the fact that before RedHat shipped GLib2 version 2.2.1 with its distribution, I temporally installed GLib2 from a tarball into /usr/local and then removed it manually?
I had a similar problem and found that it was produced by the following part of the libtool script (about line 2368):
# Find the relevant object directory and library name.
if test "X$installed" = Xyes; then
if test ! -f "$libdir/$linklib" && test -f "$abs_ladir/$linklib";then $echo "$modename: warning: library \`$lib' was moved." 1>&2
dir="$ladir"
The source of the $libdir value is from the code(about line 2285):
# Read the .la file
case $lib in
*/* | *\\*) . $lib ;;
*) . ./$lib ;;
esacThis executes the following lines in the .la file:
# Directory that this library needs to be installed in: libdir='/usr/lib'
Well, I'd mv'ed the libfreetype library from /usr/lib to /usr/X11R6/lib but somehow this libdir= wasn't changed.
In summary, the 'immediate cause' of the error message is that the <library>.la for the library in the error message has the wrong value for the rhs of the libdir assignment statement.
BTW, to the libtool maintainers: it would have helped if this information was in the error message. Something like:
the <library>.la file has inconsistent value for libdir. One
reason for this is that the library has moved.To others trying to diagnose similar errors:
I found that inserting the following lines at the top of the libtool
script:
set -x
PS4='$LINENO: '
help me find the problem. For example, the "sourcing" (i.e. . ./$lib)
of the .la file was hinted by the break in line numbers. This was
useful since searching for '+ libdir=' in the debug output produced
by just the 'set -x' was confusing._______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
