Date: Sun, 3 Jul 2011 12:24:58 +0200 From: Robert Millan <rmh@debian.org> To: Benjamin Kaduk <kaduk@mit.edu> Cc: freebsd-hackers@freebsd.org, Ed Maste <emaste@freebsd.org> Subject: Re: [PATCH] __FreeBSD_kernel__ Message-ID: <CAOfDtXPe3_Pty3GHawjX0zr-aPOsfb6siRURscaWnwBgKm19XQ@mail.gmail.com> In-Reply-To: <alpine.GSO.1.10.1107021801430.6818@multics.mit.edu> References: <CAOfDtXPUxQO1zbnxh8sh%2By7g=d8QaH2svYtEQJ06L4d%2BQKG8VA@mail.gmail.com> <alpine.GSO.1.10.1107021801430.6818@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/7/3 Benjamin Kaduk <kaduk@mit.edu>:
> % =C2=A0 =C2=A0 =C2=A0 builtin_define_with_int_value ("__FreeBSD__", FBSD=
_MAJOR); =C2=A0 =C2=A0 =C2=A0\
> % + =C2=A0 =C2=A0 builtin_define ("__FreeBSD_kernel__"); =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0\
>
> Is there a reason to prefer just defining the symbol to also including th=
e
> major version number as is done for __FreeBSD__?
None. It's just not useful from our side, but it does no harm either.
(In Debian world, there's no tight integration like you have by
putting FreeBSD kernel and compiler(s) in the same repository. A
particular version of GCC can be used to compile for one kernel or
another, so we wouldn't be able to "commit" it to a specific kernel
version)
--=20
Robert Millan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOfDtXPe3_Pty3GHawjX0zr-aPOsfb6siRURscaWnwBgKm19XQ>