Re: cvs build failure

Is it not possible to check when configure is run for the presence of the
bison output files, and only fail if one or more is absent and the bison
version is too low?

just a thought.

andrew

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Markus Bertheau" <twanger(at)bluetwanger(dot)de>; "Larry Rosenman"
<ler(at)lerctr(dot)org>; <pgsql-hackers(at)postgresql(dot)org>
Sent: Tuesday, July 01, 2003 7:10 PM
Subject: Re: [HACKERS] cvs build failure

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I can see making a new bison required only when the version is *devel.
> > That way, folks testing CVS and even the *devel snapshots would need a
> > new bison, but our normal users wouldn't.
>
> Even then, if they're using a snapshot they shouldn't need it.
>
> Perhaps a combination of your idea and Alvaro's: set things up so that
> we fail only when bison is actually invoked by the makefiles, plus
> provide a way to override the version check if it's wrong.
>
> regards, tom lane
>