Date: Sat, 9 Feb 2013 22:01:25 -0500 From: "illoai@gmail.com" <illoai@gmail.com> To: mexas@bristol.ac.uk Cc: freebsd-current@freebsd.org, freebsd@edvax.de, freebsd-questions@freebsd.org Subject: Re: building custom kernel on -current: unknown option "COMPAT_LINUX" Message-ID: <CAHHBGkp57Z%2BFSmyVf4q%2B-yhsOrHMVGXqSeVd2_YDmH1C4FtKWQ@mail.gmail.com> In-Reply-To: <201302100126.r1A1QTT2047019@mech-cluster241.men.bris.ac.uk> References: <20130210013631.4681c6fd.freebsd@edvax.de> <201302100126.r1A1QTT2047019@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9 February 2013 20:26, Anton Shterenlikht <mexas@bristol.ac.uk> wrote: > > I removed COMPAT_LINUX, and only left > > options COMPAT_43 > options COMPAT_LINUX32 > >From /usr/src/sys/amd64/conf/NOTES (9.1-RELEASE): # Enable Linux ABI emulation #XXX#options COMPAT_LINUX # Enable 32-bit Linux ABI emulation (requires COMPAT_43 and COMPAT_FREEBSD32) options COMPAT_LINUX32 I think I first ran up against this when I moved to 9.0 some time ago, but yes, amd64 uses a different kernel config option than i386 for linux compat. I tend to leave it as a module & load it if I perchance need it. This also allows rebuilding & reloading the modules without a reboot, should it need it. The modules seems to build fine without having to fiddle about with kernel config jiggerypokey. -- --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHHBGkp57Z%2BFSmyVf4q%2B-yhsOrHMVGXqSeVd2_YDmH1C4FtKWQ>