"Magnus Hagander" <mha@sollentuna.net> writes:
>> Or add a configure test to prevent it, and display a proper
>> error message.
> Yeha, I will do this.
As long as we're touching that code: the existing test for too-old bison
seriously sucks, because all that it does is to print a warning that
most people will never notice among all the other spewage from
configure. However, erroring out is not better, because for people
who're building from a tarball it won't matter what they have. The
Right Thing is to print a warning and set up for the "missing" script to
be invoked instead of bison if the files actually need to be built.
It looks like all that's needed is to reset YACC to "" after determining
that it's the wrong version, but that should be tested.
regards, tom lane