Martin Buchholz writes:
> PE> ac_func_accept_argtypes.m4 from the Autoconf macro archive addresses this
> PE> problem. There are actually more than three possible prototypes for
> PE> accept(); and the first and second argument have been known to vary as
> PE> well.
>
> Hmmm. For my purposes th
> "PE" == Peter Eisentraut <[EMAIL PROTECTED]> writes:
PE> Martin Buchholz writes:
>> Functions like accept are known to have THREE different prototypes:
>>
>> int accept (int, struct sockaddr *, socklen_t *); /* Linux, Unix98 */
>> int accept (int, struct sockaddr *, size_t *); /* Solaris 2
> "lb" == lars brinkhoff <[EMAIL PROTECTED]> writes:
lb> For comparision, this is what I use in an application of mine. I
lb> haven't heard any complaints from Solaris users, but I guess they have
lb> just ignored any compilations warnings.
I don't include . The standard says I shouldn't h
Martin Buchholz writes:
> Functions like accept are known to have THREE different prototypes:
>
> int accept (int, struct sockaddr *, socklen_t *); /* Linux, Unix98 */
> int accept (int, struct sockaddr *, size_t *); /* Solaris 2.6 */
> int accept (int, struct sockaddr *, int *); /* DEC OSF 4.0e
Martin Buchholz <[EMAIL PROTECTED]> writes:
> Functions like accept are known to have THREE different prototypes:
>
> int accept (int, struct sockaddr *, socklen_t *); /* Linux, Unix98 */
> int accept (int, struct sockaddr *, size_t *); /* Solaris 2.6 */
> int accept (int, struct sockaddr *, int
