On Tue, 2011-03-15 at 12:32 +0000, Jon TURNEY wrote: > Yes, always reproduces for non-srcdir builds for me. > > $ autoconf --version > autoconf (GNU Autoconf) 2.68 > $ automake --version > automake (GNU automake) 1.11.1 > $ git clone git://anongit.freedesktop.org/xorg/app/sessreg > [...] > $ cd sessreg > $ git describe > sessreg-1.0.6-8-g5a886e2 > $ mkdir build ; cd build > $ ../autogen.sh > [...] > $ make V=1 > make all-recursive > make[1]: Entering directory `/opt/wip/sessreg/build' > Making all in man > make[2]: Entering directory `/opt/wip/sessreg/build/man' > gcc -E -DHAVE_CONFIG_H \ > -I.. ../../man/filenames.sed.c | \ > grep 's|__' > filenames.sed > ../../man/filenames.sed.c:1:21: error: sessreg.h: No such file or > directory >
I am curious as to why we have different results. I agree with the patch, it needs to be done even if it did not fail. The difference I see is that I have autoconf 2.62 automake 1.10. I use distclean in the srcdir, then mkdir build and ../configure in their. I am trying to find out if you have a more challenging build scenario than I have. I would use it consistently as it seems to be finding more errors. I suspect 2.68 to be the difference. I recall other behavour changes with this version. Thanks for the info.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
