From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org> |
Cc: | PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ECPG won't compile anymore |
Date: | 2002-06-18 18:12:45 |
Message-ID: | 200206181812.g5IICjT10915@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-06-18 18:18:09 | Re: SetQuerySnapshot, once again |
Previous Message | Michael Meskes | 2002-06-18 17:58:10 | ecpg and bison again |