Re: What's wrong with glibc-devel-2.2 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: What's wrong with glibc-devel-2.2
Date
Msg-id 6208.987540350@sss.pgh.pa.us
Whole thread Raw
In response to What's wrong with glibc-devel-2.2  (pgsql-bugs@postgresql.org)
List pgsql-bugs
<yoda@cef.org.tw> writes:
>   I think the key point is the define of accept() in 2.2.
>   accept() define in glibc 2.2

>   extern int accept (int __fd, __SOCKADDR_ARG __addr,
>                    socklen_t *__restrict __addr_len)
>      __THROW;

>   Definition of __SOCKADDR_ARG in glibc 2.2

> #if defined __cplusplus || !__GNUC_PREREQ (2, 7)
> # define __SOCKADDR_ARG         struct sockaddr *__restrict
> # define __CONST_SOCKADDR_ARG   __const struct sockaddr *
> #else

>   Definition of __restrict in glibc 2.2

> /* __restrict is known in EGCS 1.2 and above. */
> #if !__GNUC_PREREQ (2,92)
> # define __restrict     /* Ignore */
> #endif

Looks to me like it should work; int, struct sockaddr *, socklen_t *
are one of the combinations we try for accept() arguments.  What does
config.log contain after the failure?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Lamar Owen
Date:
Subject: Re: What's wrong with glibc-devel-2.2
Next
From: David George
Date:
Subject: three VERY minor things with 7.1 final