Date: Sun, 16 Feb 1997 23:06:46 -0800 From: obrien@NUXI.com (David O'Brien) To: pst@shockwave.com (Paul Traina) Cc: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-ports@freefall.freebsd.org Subject: Re: cvs commit: src/contrib/gcc/config/i386 freebsd-elf.h freebsd.h Message-ID: <19970216230646.YW60212@dragon.nuxi.com> In-Reply-To: <199702170638.WAA21357@precipice.shockwave.com>; from Paul Traina on Feb 16, 1997 22:38:33 -0800 References: <199702162055.MAA26493@freefall.freebsd.org> <199702170638.WAA21357@precipice.shockwave.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul Traina writes: > I think you have likely already been yelled at for this, Actually, you are only the second... I expected more. > It's utterly bogus to add this symbol into gcc as a predefined symbol > because MOST 4.4 bsd systems don't have it. Ok, then how about "__post_44bsd__". > The real way to figure out if you're on a late-model BSD system is to include > sys/param.h and check for BSD >= datecode. Yes, but people simply don't do that. If anybody can offer a guarenteed way to include <sys/param.h> w/o needing to defined something like HAVE_SYS_PARAM_H in the Makefile, I'll switch all ports over to that. There has been a discussion in the ports list about this. We can be high and mightly and tell people they *will* use the BSD macro in <sys/param.h>, but it simply doesn't happen. The masses use __FreeBSD__ whether we like it or not. I want something that covers FreeBSD, NetBSD, OpenBSD, BSDI. "#if defined(__FreeBSD__) || defined(__OpenBSD__) ... " is simply ludicrist. -- -- 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?19970216230646.YW60212>