Ralf Wildenhues wrote on 2007-11-23:
> with current git, a `gnulib-tool --with-tests --test' fails like this
> if built in a VPATH build:
It does not do so for me. I'm using automake-1.10, autoconf-2.61, gcc-3.3.
Did you run "make maintainer-clean" or some such?
> The gperf-generated headers end up in the build tree
They end up in the source tree when I run "gnulib-tool --with-tests --test"
and don't run "make maintainer-clean" in the source directory. How come they
are in the build tree for you?
Anyway, I'm applying your patch. Today I prefer this to more -I options.
> make[3]: Entering directory `/tmp/build/gllib'
> depbase=`echo unictype/scripts.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
> gcc -std=gnu99 -DHAVE_CONFIG_H -DEXEEXT=\"\" -DEXEEXT=\"\"
> -DNO_XMALLOC -DEXEEXT=\"\" -I. -I../../gllib -I.. -I../intl -g -O2 -MT
> unictype/scripts.o -MD -MP -MF $depbase.Tpo -c -o unictype/scripts.o
> ../../gllib/unictype/scripts.c &&\
> mv -f $depbase.Tpo $depbase.Po
> ../../gllib/unictype/scripts.c:26:28: error: scripts_byname.h: No such file
> or directory
For me, it's different:
make[1]: entrant dans le répertoire «
/packages/GNULIB/gnulib-git/testdir29923/build/gllib »
depbase=`echo unictype/scripts.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -std=gnu99 -DHAVE_CONFIG_H -DEXEEXT=\"\" -DEXEEXT=\"\" -DNO_XMALLOC
-DEXEEXT=\"\" -I. -I.. -I../../gllib -I../intl -g -O2 -MT unictype/scripts.o
-MD -MP -MF $depbase.Tpo -c -o unictype/scripts.o
../../gllib/unictype/scripts.c &&\
mv -f $depbase.Tpo $depbase.Po
The notable difference here is the order of the -I options in DEFAULT_INCLUDES,
apparently due to a bug fix in the newer automake version that you are using.
Bruno