To: Philip Yarra <philip@utiba.com>
Cc: Michael Meskes <meskes@postgresql.org>,
	pgsql-interfaces@postgresql.org
Subject: Re: ECPG CVS version problems 
In-reply-to: <200306161404.55749.philip@utiba.com> 
References: <200303280200.h2S20N218363@candle.pha.pa.us>
	<200306161110.58418.philip@utiba.com>
	<25659.1055731774@sss.pgh.pa.us>
	<200306161404.55749.philip@utiba.com>
Comments: In-reply-to Philip Yarra <philip@utiba.com>
	message dated "Mon, 16 Jun 2003 14:04:55 +1000"
Date: Mon, 16 Jun 2003 00:35:04 -0400
Message-ID: <26338.1055738104@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

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