Re: java parser intentionally in builddir?

[Per Bothner <bothner at cygnus dot com>]

What is going on is that in the Cygnus internal source tree:
(a) the bison-generated files are not in the source tree, and
(b) they are generated into build directory, not $srcdir.

We think this makes more sense than what Gcc has done historically.
This is one distinction between our sources and the external
sources (i.e. in the past the FSF tree, now the egcs tree).
We use CYGNUS LOCAL to mark these differences to help merges.

When I merged a bunch of Java changes into egcs, I incorrectly
added the CYGNUS LOCAL version of the Makefile.in, and deleted
parse.c.  This was a mistake I intend to fix soon.

Beyond that, there is separate policy issue whether the historical
setup makes sense, and whether we are ready to change it.
Personally, I think it is a bad idea to include bison-generated
files in the respository.  I think it is reasonable to require
bison for people who want to build from cvs archives.  Note that
releases (including snapshot/alpha releases) are a different matter;
we should include the bison-generated files in those.  That is
basically a matter of making sure that bison-generated files are
generated by whatever script builds the release tar files,
just like already do for gdb and many other packages.

	--Per Bothner
Cygnus Solutions     bothner@cygnus.com     http://www.cygnus.com/~bothner