Thread: Error compiling timestamp.c in 7.4

Error compiling timestamp.c in 7.4

From
Bruno Wolff III
Date:
I get the following compiler error messages when doing a make on current CVS:
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I../../../../src/interfaces/ecpg/include
-I../../../../src/include/utils-I../../../../src/include   -g  -c timestamp.c -o timestamp.o
 
timestamp.c: In function `tm2timestamp':
timestamp.c:71: parse error before `86400000000LL'
timestamp.c:73: parse error before `long'
timestamp.c:76: parse error before `>='
timestamp.c:76: parse error before `<'
make[4]: *** [timestamp.o] Error 1

I use the following to run config:
./configure --prefix=/usr/local/pgsql --enable-integer-datetimes --with-pgport=5433

I am doing this on a RH 6.1 system.


Re: Error compiling timestamp.c in 7.4

From
Tom Lane
Date:
Bruno Wolff III <bruno@wolff.to> writes:
> I get the following compiler error messages when doing a make on current CVS:
> gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I../../../../src/interfaces/ecpg/include
-I../../../../src/include/utils-I../../../../src/include   -g  -c timestamp.c -o timestamp.o
 
> timestamp.c: In function `tm2timestamp':
> timestamp.c:71: parse error before `86400000000LL'
> timestamp.c:73: parse error before `long'
> timestamp.c:76: parse error before `>='
> timestamp.c:76: parse error before `<'
> make[4]: *** [timestamp.o] Error 1

I stuck a finger into the dike, but I think some people need to
reconsider just how far they want to push "Informix compatibility".
"#define date long" is certain to break and keep breaking our code,
and doubtless a lot of users' code too.  I'm not willing to forgo
use of that name for local variables.
        regards, tom lane


Re: Error compiling timestamp.c in 7.4

From
Bruno Wolff III
Date:
On Tue, Sep 16, 2003 at 00:38:10 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> I stuck a finger into the dike, but I think some people need to
> reconsider just how far they want to push "Informix compatibility".
> "#define date long" is certain to break and keep breaking our code,
> and doubtless a lot of users' code too.  I'm not willing to forgo
> use of that name for local variables.

Thanks. I was able to get a fresh CVS copy to work.