Date: Tue, 18 Apr 2000 08:33:35 -0700 From: Arun Sharma <adsharma@sharmas.dhs.org> To: Dirk Myers <dirkm@teleport.com> Cc: freebsd-questions@freebsd.org Subject: Re: socket.h and _POSIX_SOURCE Message-ID: <20000418083335.A3588@sharmas.dhs.org> In-Reply-To: <20000418004605.A61320@teleport.com>; from Dirk Myers on Tue, Apr 18, 2000 at 12:46:05AM -0700 References: <20000417233959.A8988@sharmas.dhs.org> <20000418004605.A61320@teleport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 18, 2000 at 12:46:05AM -0700, Dirk Myers wrote: > Look at sys/types.h -- a lot of stuff that socket.h needs to have > defined *isn't* defined if _POSIX_SOURCE is defined. > > In the error I left untrimmed above, for example, the corresponding > line from sys/socket.h is: > > typdef u_char sa_family_t; > > ... but u_char isn't defined if _POSIX_SOURCE is defined. So, this > appears to be working exactly the way it should be. I understand why the errors were happening. My question was more about if that was the intended result. > > What are you expecting having _POSIX_SOURCE defined to do for you? In other words, if I write POSIX compliant code and define _POSIX_SOURCE, I'm disallowed from using sockets ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000418083335.A3588>