Content-Type: text/plain;
  charset="iso-8859-1"
From: Philip Yarra <philip@utiba.com>
Organization: Utiba
To: Michael Meskes <meskes@postgresql.org>
Subject: Re: ECPG CVS version problems
Date: Mon, 16 Jun 2003 11:10:58 +1000
User-Agent: KMail/1.4.3
References: <200303280200.h2S20N218363@candle.pha.pa.us>
	<200304221345.40455.philip@utiba.com>
	<20030615110648.GH8944@feivel.fam-meskes.de>
In-Reply-To: <20030615110648.GH8944@feivel.fam-meskes.de>
Cc: pgsql-interfaces@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200306161110.58418.philip@utiba.com>

On Sun, 15 Jun 2003 09:06 pm, you wrote:
> [Sorry for the late answer. Somehow I didn't notice your mail wainting
> for an answer.]

No problems, I'd kinda forgotten myself.

> On Tue, Apr 22, 2003 at 01:45:40PM +1000, Philip Yarra wrote:
> > Bison 1.35 and 1.50 both have bugs that prevent successful compilation,
> > so I moved to 1.85. This appears to work okay. Is there some way during
> > configure to check for broken bison versions and complain loudly?
>
> Not that I know of.

I wondered if we could do something like:
BISON_VERSION=3D`bison -V | head -n 1 | awk '{print $4 }'`
during configure, compare the result to known buggy versions, and take some=
=20
sort of action based on that? I haven't delved into configure though, so no=
t=20
sure how to implement "some sort of action".

I think it is fairly important to try to detect these buggy bisons if the s=
ame=20
problem will be exposed in release versions of the source - it cost me quit=
e=20
a few hours trying to figure out why make was failing. I'd like to save oth=
er=20
people the hassle (and that list would include people running RedHat Linux=
=20
7.3, which includes the bison 1.35).

Regards, Philip.