Date: Tue, 22 Nov 2011 18:59:19 +0100 From: Robert Millan <rmh@debian.org> To: John Baldwin <jhb@freebsd.org> Cc: Kostik Belousov <kostikbel@gmail.com>, Adrian Chadd <adrian@freebsd.org>, freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [PATCH] Detect GNU/kFreeBSD in user-visible kernel headers Message-ID: <CAOfDtXP=nBd-PgXK0cK-SkRzFO914ryme64n8Wfix8rdX=NNmg@mail.gmail.com> In-Reply-To: <201111220824.07823.jhb@freebsd.org> References: <CAOfDtXPX1Rv9T7%2B1jYQbkM14tRY7mqgCzPcUqvHxFaRObbwvEg@mail.gmail.com> <20111121092749.GD50300@deviant.kiev.zoral.com.ua> <CAOfDtXNypUhu-dWznLyHcZMN-ZPSn_qTC6pSuL68r2M2hOjZTg@mail.gmail.com> <201111220824.07823.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/11/22 John Baldwin <jhb@freebsd.org>: > Is __FreeBSD_version defined if __FreeBSD_kernel__ is defined on kFreeBSD? Not currently (except for kernel-space code), but if all the checks that use __FreeBSD_version are like the one you describe, I think it'd make sense. But we need to make sure that defining it wouldn't suddenly enable code that is intended for FreeBSD userland, like it happens with __FreeBSD__. It'd also have to be discussed on Debian mailing list. My first impression is that defining it could be useful in some situations. We just don't run into this kind of situation so often, so this possibility AFAIK has never been discussed. I had it in my TODO to bring it up. -- Robert Millan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOfDtXP=nBd-PgXK0cK-SkRzFO914ryme64n8Wfix8rdX=NNmg>