From mboxrd@z Thu Jan 1 00:00:00 1970 From: grant.likely@secretlab.ca (Grant Likely) Date: Fri, 16 Jul 2010 11:57:55 -0600 Subject: [RFC PATCH] Kconfig: Enable Kconfig fragments to be used for defconfig In-Reply-To: <1279296221.17878.66.camel@e102109-lin.cambridge.arm.com> References: <20100713230352.6781.18644.stgit@angua> <1279296221.17878.66.camel@e102109-lin.cambridge.arm.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Jul 16, 2010 at 10:03 AM, Catalin Marinas wrote: > On Wed, 2010-07-14 at 00:04 +0100, Grant Likely wrote: >> - It still doesn't resolve dependencies. ?A solver would help with this. >> ? For the time being I work around the problem by running the generated >> ? config through 'oldconfig' and looking for differences. ?If the files >> ? differ (ignoring comments and generateconfig_* options) after oldconfig, >> ? then the _defconfig target returns a failure. ?(but leaves the >> ? new .config intact so the user can resolve it with menuconfig). ?This >> ? way at least the user is told when a Kconfig fragment is invalid. > > It's not a solver but I'm pushing a patch to warn on selecting symbols > with unmet dependencies so that you can select further symbols (manual > solving). The patch is in linux-next but you also can grab it from: > > http://git.kernel.org/?p=linux/kernel/git/cmarinas/linux-2.6-cm.git;a=commitdiff_plain;h=5d87db2d2a332784bbf2b1ec3e141486f4d41d6f sfr and I were talking about your patch the other day. Just warning on incomplete dependencies is enough to make it actually workable for me (without my ugly post-processing step). I was very happy to hear that it is in linux-next. Last missing piece is being able to do "select FOO = n", which Stephen is currently working on. g.