Re: ssize_t vs win64

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ssize_t vs win64
Date: 2010-01-02 15:29:43
Message-ID: 9837222c1001020729m4a6e1709uf2b47e6a8c8920d1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

(latest on their website as of a couple of days ago)

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-02 15:59:57 Re: ssize_t vs win64
Previous Message Peter Eisentraut 2010-01-02 15:23:12 Re: ssize_t vs win64