This doesn't look like it does what it is supposed to. At least, after applying the patch, Grammar doesn't get rebuilt at all, even when graminit.h is missing:

gcc -D_HAVE_BSDI -c -g -O2 -Wall -Wstrict-prototypes -I. -I../Include -DHAVE_CONFIG_H  -o Python/compile.o ../Python/compile.c
../Python/compile.c:17: graminit.h: No such file or directory

I can't seem to get it to make it, even though there is a $(GRAMINIT_H) dependancy. 'make Include/graminit.h' no longer works, and neither does anything else I can come up with.

But I'd like to note I'm still against rebuilding the Grammar automatically in releases :-) I'm not really sure if it's still worth rebuilding the Grammar each time, myself. It was when I did the original (horribly broken) patch, but that was in the heat of 2.0, with lots of Grammar-changing patch-proposals about.

Does this make sense?  My last change making graminit.h
and graminit.c in the build directory was wrong.  The
compiler does not understand VPATH so the include
file could not be found.  The new idea is to continue the
build even if the grammar sources cannot be regenerated
(maybe the source directory is readonly).  I don't want
to remove the target completely since someone may change
the grammar and forget to generate the source.

"If make doesn't do what you expect it to, it's a good
chance the makefile is wrong." -- BSD Make manual

Some dependances were missing.  Can you give the current
patch a whirl?  BTW, why to you think rebuilding the
grammar source is a bad idea?

Logged In: YES 
user_id=35752

Applied.  The old behavor was much too broken to leave
for the beta.