Date: Wed, 21 Jan 2015 16:25:19 -0700 From: Warner Losh <imp@bsdimp.com> To: John-Mark Gurney <jmg@funkthat.com> Cc: "freebsd-arch@freebsd.org" <arch@FreeBSD.org> Subject: opt file processing Message-ID: <672A7C0E-D710-4BB6-999E-C62D8698B442@bsdimp.com> In-Reply-To: <20150121221520.GY1949@funkthat.com> References: <201501150042.t0F0g7Um018059@svn.freebsd.org> <20150115132303.GA245@zxy.spb.ru> <368B22F3-5607-46F8-B8D2-13CA59E94861@bsdimp.com> <CAJ-Vmon1upJhjuAY8U8y376cxcqDwaVEu%2BBeOTDX5pp4TDsD1A@mail.gmail.com> <20150121221520.GY1949@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[[ Moved to arch@ ]] > On Jan 21, 2015, at 3:15 PM, John-Mark Gurney <jmg@funkthat.com> = wrote: >=20 > Adrian Chadd wrote this message on Fri, Jan 16, 2015 at 10:43 -0800: >> When I've done what you're doing, I end up having these options in my >> minimal config file so opt_xxx.h is correctly populated. That way = when >> I point SYSDIR (or whichever variable it is) at the configured kernel >> directory with the opt_xxx.h files, it all works out correctly. >>=20 >> (I still think we shouldn't be relying on "defaults", but should ship >> the opt_xxx.h files or something to derive the opt_xxx.h and makefile >> config bits so things like external module building is possible >> against a kernel. Or, we just kill all module options that change >> behaviour/ABI of things in an incompatible way.) >=20 > I have the commands that are able to stash the opt files in a kernel > section, and then be able to extract them again so that when you build > a kernel module it will use the correct options to match the kernel.. >=20 > This is most useful for things like PAE which have a big impact... I have patches in review that I need to revise that allow the modules=E2=80= =99 Makefiles to know all the opts and select to include or exclude files based on that. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?672A7C0E-D710-4BB6-999E-C62D8698B442>