# Re: \[RFC PATCH\] Kconfig: Enable Kconfig fragments to be used for defconfig

- From: Grant Likely \<hidden\>
- Date: 2010-07-16 17:58:24 
- List: linuxppc-dev
- Page: https://ratatoskr.run/linuxppc-dev/2010/07/3594385
- Thread: https://ratatoskr.run/linuxppc-dev/2010/07/3593087/t.md

```text
On Fri, Jul 16, 2010 at 10:03 AM, Catalin Marinas
[ref] wrote:
> On Wed, 2010-07-14 at 00:04 +0100, Grant Likely wrote:
>> - It still doesn't resolve dependencies. =A0A solver would help with thi=
s.
>> =A0 For the time being I work around the problem by running the generate=
d
>> =A0 config through 'oldconfig' and looking for differences. =A0If the fi=
les
>> =A0 differ (ignoring comments and generateconfig_* options) after oldcon=
fig,
>> =A0 then the <board>_defconfig target returns a failure. =A0(but leaves =
the
>> =A0 new .config intact so the user can resolve it with menuconfig). =A0T=
his
>> =A0 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=3Dlinux/kernel/git/cmarinas/linux-2.6-cm.git;a=
=3Dcommitdiff_plain;h=3D5d87db2d2a332784bbf2b1ec3e141486f4d41d6f

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 =3D n", which Stephen
is currently working on.

g.
```
