From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> |
Cc: | Postgresql <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: ecpg long int problem on alpha + fix |
Date: | 2001-04-04 12:02:53 |
Message-ID: | 20010404140253.A31232@feivel.credativ.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 03, 2001 at 06:32:25PM +0300, Adriaan Joubert wrote:
> we had a problem on Alpha that in interfaces/ecpg/lib/typename.c we
> have
> HAVE_LONG_INT_64 defined, but not HAVE_LONG_LONG_INT_64. Consequently no
Sure since that means your long int and not your long long int is 64 bits.
> code is included for long ints and typename calls *abort*. I put in a
> few lines that check for HAVE_LONG_INT_64 and seem to generate the right
Why is this needed? What you do is use "long long" as variable type for 64
bits integer. But on the alpha you do not need "long long", just use "long
int" instead.
Or did I misunderstand something?
Michael
--
Michael Meskes
Michael(at)Fam-Meskes(dot)De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Adriaan Joubert | 2001-04-04 12:35:34 | Re: ecpg long int problem on alpha + fix |
Previous Message | The Hermit Hacker | 2001-04-04 11:53:19 | All's quiet ... RC3 packaging ... |