On Mon, 18 Apr 2011, Jim Meyering wrote: > FYI, now, using the latest sources from git, > when I bootstrap, run ./configure --enable-gcc-warnings > and then make and "make distcheck", I see this: > > /bin/sh ../build-aux/ylwrap ../src/parse-gram.y y.tab.c src/parse-gram.c > y.tab.h src/parse-gram.h y.output src/parse-gram.output -- tests/bison -y -dv > --warnings=all,error --report=all > /bin/sh ../build-aux/ylwrap ../src/scan-code.l lex.yy.c src/scan-code.c -- > flex > /bin/sh ../build-aux/ylwrap ../src/scan-gram.l lex.yy.c src/scan-gram.c -- > flex > /bin/sh ../build-aux/ylwrap ../src/scan-skel.l lex.yy.c src/scan-skel.c -- > flex > /w/bison/bison-2.4.593-a78a/_build/tests/bison: line 11: > /w/bison/bison-2.4.593-a78a/_build/src/bison: No such file or directory > Can't open y.tab.[ch]: No such file or directory. > make[1]: *** [src/parse-gram.c] Error 1 > make[1]: *** Waiting for unfinished jobs.... > make[1]: Leaving directory `/w/bison/bison-2.4.593-a78a/_build' > make: *** [distcheck] Error 1
This doesn't happen for me. Somehow your tarball's parse-gram.y must have a later time stamp than parse-gram.c or parse-gram.h. Is your "make dist" setting the time stamps inappropriately for some reason? If so, perhaps we need a dist-hook to fix that. Or are the time stamps being set inappropriately upon extraction from the tarball?
