Re: pgsql: Define INADDR_NONE on Solaris when it's missing.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-committers <pgsql-committers@postgresql.org>
Date: 2010-01-28T16:04:37Z
Lists: pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes: > On Thu, Jan 28, 2010 at 16:46, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Possibly more to the point, where are we using INADDR_NONE anyway? > In the RADIUS code. Oh, that's why it isn't in my tree and has zero portability track record ... I think what this shows is we should look for a way to avoid using INADDR_NONE. What's your grounds for believing it's portable at all? In the Single Unix Spec I only see INADDR_ANY and INADDR_BROADCAST defined. regards, tom lane