Re: ECPG won't compile anymore - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: ECPG won't compile anymore
Date
Msg-id 200206181812.g5IICjT10915@candle.pha.pa.us
Whole thread Raw
In response to Re: ECPG won't compile anymore  (Michael Meskes <meskes@postgresql.org>)
Responses Re: ECPG won't compile anymore  (Michael Meskes <meskes@postgresql.org>)
List pgsql-hackers
Michael Meskes wrote:
> On Tue, Jun 18, 2002 at 10:29:10AM -0400, Tom Lane wrote:
> > I'd be inclined to say that you don't commit until bison 1.49 is
> > officially released.  Got any idea when that will be?
> 
> No, that's the problem. ECPG and the backend parser are running out of
> sync. After all bison's release may be later than our next one. 
> 
> I cannot commit even simple bugfixes anymore as my source tree
> already has the uncompilable bison file. So I would have to work on two
> different source trees. I don't exactly like that.

Are we the only ones up against this problem?  Hard to imagine we are
the only ones up against this limit in bison.  Are there other options? 
I don't see how we can distribute ecpg in 7.3 without some kind of fix.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Michael Meskes
Date:
Subject: ecpg and bison again
Next
From: Tom Lane
Date:
Subject: Re: SetQuerySnapshot, once again