From owner-freebsd-current Wed Feb 5 02:39:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA06641 for current-outgoing; Wed, 5 Feb 1997 02:39:01 -0800 (PST) Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA06631 for ; Wed, 5 Feb 1997 02:38:57 -0800 (PST) From: garyj@frt.dec.com Received: from cssmuc.frt.dec.com by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV) id FAA14153; Wed, 5 Feb 1997 05:33:27 -0500 (EST) Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM) id AA17951; Wed, 5 Feb 1997 11:33:16 +0100 Message-Id: <9702051033.AA17951@cssmuc.frt.dec.com> X-Mailer: exmh version 1.6.4 10/10/95 To: current@freebsd.org In-Reply-To: Message from Warner Losh of Tue, 04 Feb 97 18:20:28 MST. Reply-To: gjennejohn@frt.dec.com Subject: Re: conditionally including Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Feb 97 11:33:16 +0100 X-Mts: smtp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk imp@village.org 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. > what I'd lioke to see in -current (aka 3.0) is __FreeBSD__=3 instead of __FreeBSD__=2. This would make it easier to differentiate between 2.2 and 3.0. At the moment they both define BSD the same, so it's not possible to use BSD to tell 'em apart. I'm helping to maintain some kernel code which compiles on all FreeBSD versions > 2, but 3.0 requires some special handling and I'm not aware of a reliable way to check whether I'm compiling under 2.2 or 3.0. If anyone knows of a good mechanism, please pipe up. --- Gary Jennejohn (work) gjennejohn@frt.dec.com (home) Gary.Jennejohn@munich.netsurf.de (play) gj@freebsd.org