From owner-freebsd-hackers Sat Apr 12 12:10:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA16524 for hackers-outgoing; Sat, 12 Apr 1997 12:10:35 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA16510 for ; Sat, 12 Apr 1997 12:10:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA15492; Sat, 12 Apr 1997 11:50:18 -0700 From: Terry Lambert Message-Id: <199704121850.LAA15492@phaeton.artisoft.com> Subject: Re: detecting kernel version at compile time To: avalon@coombs.anu.edu.au (Darren Reed) Date: Sat, 12 Apr 1997 11:50:18 -0700 (MST) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199704120302.UAA28710@coyote.Artisoft.COM> from "Darren Reed" at Apr 12, 97 12:37:31 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hmmm, can __FreeBSD_sysversion be made the same value as __FreeBSD_version ? > (or vice versa) The easiest way is to install only RELEASE version of the OS, and don't update your kernel or user space sources until the next RELEASE. It turns out that that also happens to be the easiest situation for a commercial vendor to support, so everyone gets to be happy. 8-). > The problem with __FreeBSD__ is that it is defined by cc - or gcc/pgcc. > > That is, it depends on what system the compiler is built, not what OS > it is running on. > > Problem being, it impacts every compilation thereafter. I do not use the __FreeBSD__ tag, personally. There is *some* use of the tag in the NFS cokkie code, since there is an inversion of operation order between FreeBSD and Net/OpenBSD. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.