The mingw header has pretty much this with WINSOCK_API_LINKAGE IN OUT
and FAR dissolved away.
The standard test complains about it being an unresolved reference when
it is declared as "char getaddrinfo (); ". If we remove that and instead
include the header the test passes. I have no idea why that should be
the case for this function and not for others.
cheers
andrew
Chuck McDevitt wrote:
The definition in WS2tcpip.h
WINSOCK_API_LINKAGE
int
WSAAPI
getaddrinfo(
IN const char FAR * nodename,
IN const char FAR * servname,
IN const struct addrinfo FAR * hints,
OUT struct addrinfo FAR * FAR * res
);
(IN, FAR, and OUT are #defined to empty string).
WINSOCK_API_LINKAGE is __declspec(dllimport)
WSAAPI is __stdcall
So, nothing magic with #defines of the name getaddrinfo.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Thursday, August 18, 2005 3:47 PM
To: Andrew Dunstan
Cc: PostgreSQL-development
Subject: Re: [HACKERS] Windows + IP6 progress
Andrew Dunstan <[EMAIL PROTECTED]> writes:
. what do we do about the getaddrinfo test? I'm almost inclined not
to
do it on windows, and assume that if we have ws2_32.dll we have it.
There's something mighty fishy about that. AC_REPLACE_FUNCS works on
Windows for the other cases it's used for (no?), so what's different
about getaddrinfo? Perhaps Microsoft has #define'd that name as
something else, or some equally ugly crock? It'd be useful to look
into
their header files and see exactly how and where getaddrinfo is
declared.
regards, tom lane
---------------------------(end of
broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
