From owner-freebsd-questions Tue Apr 18 8:33:52 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 8485537BA03 for ; Tue, 18 Apr 2000 08:33:50 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id IAA03627; Tue, 18 Apr 2000 08:33:35 -0700 Date: Tue, 18 Apr 2000 08:33:35 -0700 From: Arun Sharma To: Dirk Myers Cc: freebsd-questions@freebsd.org Subject: Re: socket.h and _POSIX_SOURCE Message-ID: <20000418083335.A3588@sharmas.dhs.org> References: <20000417233959.A8988@sharmas.dhs.org> <20000418004605.A61320@teleport.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000418004605.A61320@teleport.com>; from Dirk Myers on Tue, Apr 18, 2000 at 12:46:05AM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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