Re: ssize_t vs win64

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ssize_t vs win64
Date: 2010-01-02 23:20:48
Message-ID: 1262474448.3542.2.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On lör, 2010-01-02 at 16:29 +0100, Magnus Hagander wrote:
> On Sat, Jan 2, 2010 at 16:23, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> > On lör, 2010-01-02 at 15:42 +0100, Magnus Hagander wrote:
> >> When trying to build plpython on win64, it fails because ssize_t is
> >> defined differently.
> >>
> >> PostgreSQL has it as
> >> typedef long ssize_t;
> >>
> >> And python has it as:
> >> typedef __int64 ssize_t;
> >
> > What file/line is that? I don't see that in my copies.
>
> You mean in python? It's in pyconfig.h, line 205 (the version
> manually maintained for non-autoconf platforms). The version I have
> is:
> Python 2.6.4 (r264:75708, Oct 26 2009, 07:36:50) [MSC v.1500 64 bit
> (AMD64)] on win32

Seems kind of buggy. They shouldn't be defining it at all.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-01-02 23:24:51 Re: ssize_t vs win64
Previous Message Andrew Dunstan 2010-01-02 22:50:40 Re: invalid UTF-8 via pl/perl