Date: 11 Nov 2002 16:36:58 +0100 From: Marc Recht <marc@informatik.uni-bremen.de> To: Mike Barcroft <mike@FreeBSD.ORG> Cc: Garrett Wollman <wollman@lcs.mit.edu>, current@FreeBSD.ORG Subject: Re: addition to cdefs Message-ID: <1037029019.779.87.camel@leeloo.intern.geht.de> In-Reply-To: <20021111095458.F52940@espresso.q9media.com> References: <1037017897.779.20.camel@leeloo.intern.geht.de> <20021111095458.F52940@espresso.q9media.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Thanks! > It looks like <unistd.h> has some XSI bugs. Is _XOPEN_SOURCE defined > anywhere? If so, try the attached patch. If not, this is a bug in Yes, _XOPEN_SOURCE is defined. So, it solves some of the problems. > Python (since POSIX doesn't specify chroot()) and should be fixed at > their end and in the ports collection. But, there still some problems left. Like fd_set being not defined in sys/select if _BSD_VISIBLE isn't given. > _BSD_SOURCE provides mostly the same visibility as not defining any > standards constants, so it isn't very useful. IMO it would be nice to have a clean way to toggle __BSD_VISIBLE from the outside. In the default environment I have #define __POSIX_VISIBLE 200112 #define __XSI_VISIBLE 600 #define __BSD_VISIBLE 1 #define __ISO_C_VISIBLE 1999 But, Python for example, wants _POSIX_C_SOURCE 199506,_XOPEN_SOURCE 500 _and_ __BSD_VISIBLE 1. I know, I could also just do a -D__BSD_VISIBLE=1, but I think thats not The Right Thing to do. Regards, Marc -- "Premature optimization is the root of all evil." -- Donald E. Knuth [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA9z86a7YQCetAaG3MRAuoUAJ9JBtq6GZT6HBBdtmg79O3E9KJLxwCdH/o3 LfHkp9q1xk6wvxT0CWNosE8= =Xp4F -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1037029019.779.87.camel>