Re: `configure' and `make/bison' build issues

[Brian Dessent]

Eric Blake wrote:

> Actually, it is very common to get conflicts in generated files, when the
> version of the generator is different between the person who checked into
> cvs vs. the person doing the build (for example autoconf 2.59 vs 2.59c).
> That's why so many projects try to avoid generated files in CVS, and
> instead have a huge bootstrap script that requires a user to install
> prerequisite generator tools.

Certainly differences in autotools versions will cause conflicts in
generated files.  But I guess the point I was trying to convey was that
in such cases where generated files like 'configure' are stored in CVS,
in almost all casual usage patterns (i.e. checking out the source just
to build the package or perhaps make minor changes) the checked out copy
will be used without needing to be rebuilt.  It is only the developer
who actually modifies a configure.ac or similar input file that would
ever set the stage for a conflict in a generated file, and this type of
change is comparitively rare -- certainly not something that I would
expect from the OP who stated that he has yet to successfully build the
package at all.

Brian