Re: Is there a way to build PostgreSQL client libraries with MinGW - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Is there a way to build PostgreSQL client libraries with MinGW
Date
Msg-id 4D4182EF.5080709@dunslane.net
Whole thread Raw
In response to Re: Is there a way to build PostgreSQL client libraries with MinGW  (Xiaobo Gu <guxiaobo1982@gmail.com>)
List pgsql-hackers

On 01/27/2011 09:19 AM, Xiaobo Gu wrote:
> On Thu, Jan 27, 2011 at 10:01 PM, Andrew Dunstan<andrew@dunslane.net>  wrote:
>>
>> On 01/27/2011 08:51 AM, Robert Haas wrote:
>>> On Thu, Jan 27, 2011 at 7:31 AM, Xiaobo Gu<guxiaobo1982@gmail.com>    wrote:
>>>> 20:25<jon_y>: please contact psql and ask for a list of accept()
>>>> implementations checked
>>> It looks like we check each argument and the return type for a couple
>>> of possibilities:
>>>
>>> argument 1 can be int or unsigned int
>>> argument 2 can be struct sockaddr * or const struct sockaddr * or void *
>>> argument 3 can be int * or size_t * or socklen_t * or unsigned int * or
>>> void *
>>> the return type can be int or unsigned int PASCAL
>>>
>>>
>> Yeah. it looks like the return type is the likely culprit. It looks like it
>> wants either a signed or unsigned int64. Also, the mingw64 API uses the
>> WSAAPI qualifier instead of PASCAL.
>>
> I am still trying, but I think it may be the first argument, because
> MinGW64 define SOCKET as a pointer, but you accept int or unsigned int
>

No it doesn't. It defines it as an INT_PTR or UINT_PTR which in turn is 
an __int64, I think. But you're right, we might need to look at the 
first argument as well as the return type.

cheers

andrew


pgsql-hackers by date:

Previous
From: Xiaobo Gu
Date:
Subject: Re: Is there a way to build PostgreSQL client libraries with MinGW
Next
From: Tom Lane
Date:
Subject: Re: ALTER TYPE 3: add facility to identify further no-work cases