re: sys/socket.h and source defines

[matthew green <mrg@eterna.com.au>]

   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


can you post the exactly problems?  this sounds more like broken packages
defining things (_POSIX_SOURCE and/or _XOPEN_SOURCE) incorrectly...  you
can't just define it for some system headers and not others!


.mrg.