Re: BUG #6238: ECPG converts "long long" to long on Windows

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, Jim Gray <jim(dot)gray(at)bull(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6238: ECPG converts "long long" to long on Windows
Date: 2011-10-04 14:44:22
Message-ID: 1317739247-sup-2334@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Excerpts from Robert Haas's message of mar oct 04 10:39:27 -0300 2011:
> On Tue, Oct 4, 2011 at 8:15 AM, Michael Meskes <meskes(at)postgresql(dot)org> wrote:

> >> 2010 on Windows, which accepts "long long" to mean the same thing as
> >> __int64, but ECPG doesn't recognize the later.
> >> May be related to BUG #5464: ecpg on 64bit system converts "long long" to
> >> "long"
> >
> > Well, this bug is (at least I don't know otherwise) fixed for more than a year.
> > Maybe the configure test doesn't work on Windows? I don't know.
>
> On at least some Windows builds, configure isn't used at all... so
> whatever values is being used would come from the MSVC build system.

In fact, pg_config.h.win32 does not have the HAVE_LONG_LONG_INT symbol
at all -- only HAVE_LONG_LONG_INT_64 is in there.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jim.Gray 2011-10-04 17:02:54 Re: BUG #6237: Hang during install database initialization
Previous Message Robert Haas 2011-10-04 13:39:27 Re: BUG #6238: ECPG converts "long long" to long on Windows