libtool VPATH build

[Bob Friesenhahn]

It seems that Gary has been naughty and did not test CVS head with a 
VPATH build before allowing himself the pleasure of a vacation.

When configure/make is done from outside the source tree, the build 
can not find the libltdl headers.

This annoying situation is compounded by the fact that executing the 
'bootstrap' script takes almost 9 minutes on a dual Pentium IV 2.4 GHz 
Xeon system.  I would hate to think about how long it would take on a 
slower system.

 /usr/local/bin/gcc-3.4.0 "-DHAVE_CONFIG_H=<config.h>" -DLTDL -I. 
-I/home/bfriesen/src/gnu/libtool/libltdl/loaders -I../.. -I../../.. 
-I/home/bfriesen/src/gnu/libtool/.. -I.. 
-I/home/bfriesen/src/gnu/libtool/libltdl/loaders/.. 
-I/usr/local/include -O2 -Wall -march=i686 -pipe -MT dlopen.lo -MD -MP 
-MF .deps/dlopen.Tpo -c 
/home/bfriesen/src/gnu/libtool/libltdl/loaders/dlopen.c  -fPIC -DPIC 
-o .libs/dlopen.o
In file included from 
/home/bfriesen/src/gnu/libtool/libltdl/loaders/dlopen.c:30:
/home/bfriesen/src/gnu/libtool/libltdl/loaders/../lt_dlloader.h:33:31: 
libltdl/lt_system.h: No such file or directory
In file included from 
/home/bfriesen/src/gnu/libtool/libltdl/loaders/dlopen.c:30:
/home/bfriesen/src/gnu/libtool/libltdl/loaders/../lt_dlloader.h:37: 
error: syntax error before "typedef"

There are odd things with the include path.  Notice that the include 
path is searching outside the libtool directory where non-libtool 
files may reside.

Bob
======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen