Date: Tue, 27 Jan 2015 16:06:11 -0700 From: Warner Losh <imp@bsdimp.com> To: Garrett Cooper <yaneurabeya@gmail.com> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers <src-committers@freebsd.org>, Garrett Cooper <ngie@FreeBSD.org> Subject: Re: svn commit: r277681 - in head/sys: conf modules Message-ID: <1080CE66-04D2-4EB4-9A31-CC130F447FCF@bsdimp.com> In-Reply-To: <5CC0EF20-0DDC-4082-BD2A-5DD64822B03D@gmail.com> References: <201501250513.t0P5DGoc033955@svn.freebsd.org> <0CF820AF-D73D-4CE8-BE5B-C4EBE5A9EFDA@bsdimp.com> <5CC0EF20-0DDC-4082-BD2A-5DD64822B03D@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Jan 26, 2015, at 7:30 PM, Garrett Cooper <yaneurabeya@gmail.com> wrote: > > On Jan 25, 2015, at 9:46, Warner Losh <imp@bsdimp.com> wrote: > >> The number of MK_foo opts that are intruding into the kernel module builds is >> starting to get out of hand. :( Especially since they are duplicative of the >> MODULES_OVERRIDE functionality and are very unevenly applied. > > I don’t really like it either to be honest, but the problem is that building MK_CUSE == no (for instance) should produce a working default set of SUBDIRs so both the kernel and userland infrastructure are compiled with the build. Telling someone to use MODULES_OVERRIDE to just remove cuse (for instance), is a user unfriendly system.. > > If there was a way to pick up a subset of src.opts.mk though and apply it to kern.opts.mk, I would be incredibly keen on making that change. There isn’t. That’s the problem with the current setup. It isn’t always clear to me that if you disable the user land side you necessarily want to disable the kernel side, but it is the best indication we have. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1080CE66-04D2-4EB4-9A31-CC130F447FCF>