| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ECPG |
| Date: | 2002-09-24 13:53:10 |
| Message-ID: | 12627.1032875590@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Meskes <meskes(at)postgresql(dot)org> writes:
> On Mon, Sep 23, 2002 at 09:56:59AM -0400, Tom Lane wrote:
>> What about removing this feature that used to exist: being able to build
>> ecpg with reasonably-standard tools?
> How many people do use bison themselves?
*Everyone* who checks out from our CVS needs to build the bison output
files. There seem to be quite a few such people; they will all be
forced to upgrade their local bison installations when ecpg starts
requiring a newer bison.
> I will try to get some info from the bison people about the release
> date.
I just this morning got this response from Akim Demaille concerning a
portability problem in bison 1.49b:
| Thanks for the report, this is addressed in 1.49c. We should upload
| the latter soon.
So I'm guessing that a full release is not just around the corner :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roland Roberts | 2002-09-24 14:55:41 | Re: [SQL] CURRENT_TIMESTAMP |
| Previous Message | Neil Conway | 2002-09-24 13:50:02 | making use of large TLB pages |