From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org> |
Cc: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com>, Postgresql <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ecpg long int problem on alpha + fix |
Date: | 2001-04-04 14:04:46 |
Message-ID: | 1675.986393086@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:
>> all exist on alpha and are all 64 bits, but HAVE_LONG_LONG_INT_64 is not
>> defined, so ecpg cannot handle ECPGt_long_long types. It is not clear to
> I see. I was under the impression that HAVE_LONG_LONG_INT_64 should be
> defined if long long int is 64 bit integer which of course it is on the
> alpha.
No! Look at the configure test! It doesn't bother to investigate long
long int if it finds that long int will serve. At most one of the two
symbols will be defined. I believe that that is the correct way, at
least for the backend's purposes, since we only want to compile one set
of int64-related code.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2001-04-04 14:33:27 | Re: Final call for platform testing |
Previous Message | Tom Lane | 2001-04-04 13:59:37 | Re: All's quiet ... RC3 packaging ... |