On Fri, Jul 04, 2003 at 11:23:57 -0700,
Joe Conway <[EMAIL PROTECTED]> wrote:
>
> Thanks, Tom. It does at least compile cleanly now. I don't use ecpg, so
> I can't say whether the changes actually work.
I am still seeing the problem in anoncvs, but I seem to remember there being
a lag between
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
Yeah, I've been getting that since Wednesday morning (west coast USA
time), and reported it Wednesday evening, but no one else has replied to
that post, so I thought maybe it was somehow related to the othee ecpg
issues being discussed.
I
Joe Conway <[EMAIL PROTECTED]> writes:
> Yeah, I've been getting that since Wednesday morning (west coast USA
> time), and reported it Wednesday evening, but no one else has replied to
> that post, so I thought maybe it was somehow related to the othee ecpg
> issues being discussed.
I've commit
Bruno Wolff III wrote:
I get the following compilation error when making postgres from current CVS:
timestamp.c: In function `tm2timestamp':
timestamp.c:69: warning: implicit declaration of function `elog'
timestamp.c:69: `ERROR' undeclared (first use in this function)
timestamp.c:69: (Each undecla
I get the following compilation error when making postgres from current CVS:
timestamp.c: In function `tm2timestamp':
timestamp.c:69: warning: implicit declaration of function `elog'
timestamp.c:69: `ERROR' undeclared (first use in this function)
timestamp.c:69: (Each undeclared identifier is repor
