Re: sys/socket.h and source defines
On Mon, Feb 18, 2002 at 06:42:31PM -0500, utsl@quic.net wrote:
> On Mon, Feb 18, 2002 at 04:19:56PM -0700, Joel Baker wrote:
> > As best I can tell, with the native NetBSD sys/socket.h, if a problem in
> > any way defines (or triggers definition of) _POSIX_SOURCE or _XOPEN_SOURCE,
> > anything which calls sys/socket.h will break horribly (since it uses values
> > from types.h - which it also fails to include on it's own - which are only
> > valid if not using POSIX sources, specifically u_char rather than u_int8_t)
> >
> > Can anyone offer solutions to this? It's breaking a number of packages
> > which, for various reasons, declare one of these two, and then include some
> > file which, in turn, includes sys/socket.h
>
> I'd look at adding #ifdef's into sys/socket.h to switch to u_int8_t if
> _POSIX_SOURCE is defined.
This is a fix I had considered... but really should happen upstream. I
guess perhaps I'll check the CVS version of things, and file a bug if it's
still got this problem...
--
***************************************************************************
Joel Baker System Administrator - lightbearer.com
lucifer@lightbearer.com http://users.lightbearer.com/lucifer/
Reply to: