On Mon, Apr 19, 2004 at 11:18:07AM -0400, Tom Lane wrote:
>
> What you'd need to do is determine which system headers are being
> #include'd by that config test, and then look through them to find
> struct addrinfo.
Well, I have this in /usr/include/netdb.h:
struct addrinfo {
int ai_flags; /* AI_PASSIVE, AI_CANONNAME,
AI_NUMERICH
OST */
int ai_family; /* PF_xxx */
int ai_socktype; /* SOCK_xxx */
int ai_protocol; /* 0 or IPPROTO_xxx */
size_t ai_addrlen; /* length of ai_addr */
char *ai_canonname; /* canonical name for
hostname */
struct sockaddr *ai_addr; /* binary address */
struct addrinfo *ai_next; /* next structure in list */
};
Using the cpp trick that Alvaro Herrera suggested, I see that file
mentioned in the output, and this a little way along:
struct addrinfo {
int ai_flags;
int ai_family;
int ai_socktype;
int ai_protocol;
size_t ai_addrlen;
char *ai_canonname;
struct sockaddr *ai_addr;
struct addrinfo *ai_next;
};
So it looks like that must be the one. Dunno if this helps.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
