java parser intentionally in builddir?

[Joe Buck]

[ bison output files ]

RJL writes:
> The reason this caught my attention is that I build on a handful of
> hosts for a handful of targets.  Only one host has all the funky tools
> required for EGCS snapshot building.  This was fine until this change
> in Java was made.  Now I either have to have bison everywhere or "fix"
> java/Makefile.in.

It seems that the logical thing to do is to avoid shipping derived files,
but build platform-independent derived files in the source directory.
(This is the method I use in my own work, for the same reason as RJL
uses it ... I don't even have the required tools for all platforms).

(However, I could live with it if you decide to put the bison output
in the binary directory ... multi-platform builds could do symbolic
links).