Re: problems with configure - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: problems with configure
Date
Msg-id Pine.LNX.4.21.0011091707110.1244-100000@peter.localdomain
Whole thread Raw
In response to Re: problems with configure  (pete.forman@westgeo.com)
Responses Re: problems with configure  (Pete Forman <pete.forman@westgeo.com>)
Re: problems with configure  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
pete.forman@westgeo.com writes:

> Depending on the version of Solaris and the compiler flags the third
> argument can be a pointer to socklen_t, void, size_t or int.

I think what I'm going to do is this:  The argument is question cannot
possibly be of a different width than int, unless someone is *really* on
drugs at Sun.  Therefore, if the third argument to accept() is "void *"
then we just take "int".  Evidently there will not be a compiler problem
if you pass an "int *" where a "void *" is expected.  The fact that int
may be signed differently than the actual argument should not be a
problem, since evidently the true argument type varies with compiler
options, but surely the BSD socket layer does not.

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Schemas (Re: AW: Unhappy thoughts about pg_dump and objects inherited from template1)
Next
From: Philip Warner
Date:
Subject: Re: AW: AW: Unhappy thoughts about pg_dump and objects inherited from template1