Date: Wed, 6 Jul 2011 08:53:32 +0200 From: Robert Millan <rmh@debian.org> To: Ed Maste <emaste@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] __FreeBSD_kernel__ Message-ID: <CAOfDtXN_xi-K9z1N%2BA4RPcUbuQmZ7cMgPpf_VCRYPL_gkLUT6w@mail.gmail.com> In-Reply-To: <20110705201214.GA31647@sandvine.com> References: <CAOfDtXPUxQO1zbnxh8sh%2By7g=d8QaH2svYtEQJ06L4d%2BQKG8VA@mail.gmail.com> <20110702193724.5c55a6c9@kan.dnsalias.net> <20110703020827.GA5763@sandvine.com> <CAGH67wQAv4Tf8HjccN2GZzgD2u1ZrORABtGehxXjeg109%2BRNWQ@mail.gmail.com> <20110703103531.4a553271@kan.dnsalias.net> <CAOfDtXOcfbNw6St5CMN4GB_psf8hZEV=hpL4q3mmQXqWeLmqXQ@mail.gmail.com> <20110705140527.17362ed5@kan.dnsalias.net> <20110705201214.GA31647@sandvine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/7/5 Ed Maste <emaste@freebsd.org>: > On the topic of where such a macro should be defined I originally had > no strong opinion. =C2=A0However, valid points have been raised about > compiling software for FreeBSD using compilers that are not the one in > the base system (from ports or otherwise, and GCC or otherwise). =C2=A0Th= is > I think is a very valid point and one that would make me lean towards > defining the macro in sys/param.h. =C2=A0How workable is it to #include > sys/param.h to pick up the macro where needed? That works most of the time. There could be a problem if software can't assume <sys/param.h> is present, but I think it covers the vast majority of cases. --=20 Robert Millan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOfDtXN_xi-K9z1N%2BA4RPcUbuQmZ7cMgPpf_VCRYPL_gkLUT6w>