Skip site navigation (1) Skip section navigation (2)

Re: ECPG CVS version problems

From: Philip Yarra <philip(at)utiba(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>,pgsql-interfaces(at)postgresql(dot)org
Subject: Re: ECPG CVS version problems
Date: 2003-06-16 05:58:13
Message-ID: 200306161558.13871.philip@utiba.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfacespgsql-patches
On Mon, 16 Jun 2003 02:35 pm, Tom Lane wrote:
> Philip Yarra <philip(at)utiba(dot)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 [it] in configure's output

Oh, yes, well so it is. Sorry about that.

>  (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.)

Provided preproc.y has changed... `make clean` does not remove the output of 
bison, I found. When I copied the CVS source from my workstation to the 
machine with older bison I didn't realise that, hence the confusion.

> > I assume that a way was found to make
> > older versions of bison work
>
> You assume wrong.  

Yep. Part of the learning-curve, I suppose. I'll get there.

Regards, Philip.

In response to

pgsql-hackers by date

Next:From: Michael MeskesDate: 2003-06-16 06:01:11
Subject: Re: ECPG CVS version problems
Previous:From: Oleg BartunovDate: 2003-06-16 05:57:55
Subject: Re: [HACKERS] UTF8 and KOI8 mini-howto

pgsql-patches by date

Next:From: Michael MeskesDate: 2003-06-16 06:01:11
Subject: Re: ECPG CVS version problems
Previous:From: Tom LaneDate: 2003-06-16 05:18:24
Subject: Re: ECPG CVS version problems

pgsql-interfaces by date

Next:From: Michael MeskesDate: 2003-06-16 06:01:11
Subject: Re: ECPG CVS version problems
Previous:From: Tom LaneDate: 2003-06-16 05:18:24
Subject: Re: ECPG CVS version problems

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group