Date: Wed, 5 Feb 1997 00:33:43 -0800 From: obrien@NUXI.com (David O'Brien) To: imp@village.org (Warner Losh) Cc: freebsd-ports@FreeBSD.ORG (FreeBSD ports list), hackers@FreeBSD.ORG Subject: Re: conditionally including <sys/param.h> Message-ID: <19970205003343.YB13323@dragon.nuxi.com> In-Reply-To: <E0vrw2G-0000I7-00@rover.village.org>; from Warner Losh on Feb 4, 1997 18:20:28 -0700 References: <19970202135048.PN07710@dragon.nuxi.com> <199701280143.RAA06503@freefall.freebsd.org> <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu> <E0vrw2G-0000I7-00@rover.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh writes: > In message <19970202135048.PN07710@dragon.nuxi.com> David O'Brien writes: > : to get a new cpp symbol added (like __44bsd__ or something). > > This is a bad idea, since it has lost a lot of its potential meaning > with so many 44bsd derived systems that pick and chose between 4.4 and > 4.4 Lite 2. Then what would you suggest? Are they really more different than all the various sysVr4 that define __svr4__? How close is Solaris, UnixWare, and Irix? I'm just trying to find something that will cover all the 4.4BSD derived OS's. What are the big divergances from each other that __44bsd__ wouldn't cover (from an application standpoint)? Remember I'm trying to catch things like sys_errlist[], termios, /var/mail, /usr/sbin/sendmail, etc. Everyone will acknowlege that for kernel stuff __FreeBSD__, etc. should be used. But I still think __44bsd__ is fine where we would already do the #if (BSD > xyx) test or defined(__FreeBSD__) || defined(__NetBSD__) ,etc. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970205003343.YB13323>