I wonder is we should check for *dev on the version string and make
missing bison version a hard error in these cases.
---------------------------------------------------------------------------
Tom Lane wrote:
> Philip Yarra <philip@utiba.com> writes:
> > I just did a test build on a machine with bison 1.35, and there were no
> > complaints regarding its version
>
> You sure? I see in configure's output
>
> ...
> checking whether it is possible to strip libraries... yes
> checking for bison... bison -y
> configure: WARNING:
> *** The installed version of Bison is too old. PostgreSQL needs
> *** Bison version 1.875 or later.
> checking for perl... /usr/bin/perl
> checking for main in -lbsd... yes
> ...
>
> which admittedly is easy to miss, but it's there. (The reason it's not
> a hard error is that you don't actually need bison unless you don't have
> up-to-date copies of the derived files made by bison. This should not
> be the case when using a snapshot, only when building from a CVS pull.)
>
> > I assume that a way was found to make
> > older versions of bison work
>
> You assume wrong. Not all the .y files need recent bison, but the ones
> that do will fail badly. The issues are grammar-size limits for bison
> less than about 1.50, and outright bison bugs for versions from there to
> 1.875. We do not have workarounds.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073