On Wed, Aug 10, 2011 at 10:17 AM, David Woodhouse <dwmw2@xxxxxxxxxxxxx> wrote: > On Wed, 2011-08-10 at 10:15 -0400, Arnaud Lacombe wrote: >> >> hum, let's take a real life example: user foo wants his config to >> enable CONFIG_WIRELESS_EXT, so with what you propose, he would do: >> >> # make CONFIG_WIRELESS_EXT=y allmodconfig >> >> currently, this would _never_ work, unless one of the symbol selected >> by `allmodconfig' selects it, as WIRELESS_EXT is defined the >> following: >> >> config WIRELESS_EXT >> bool >> >> I suspect there also an implicit dependency to WIRELESS. > > This is a complete red herring. It's *always* been like that, and works > *just* like this for the 'all.config' file etc. > your point being ? I might as well tell you that I find the current behavior of 'all*.config' just as broken wrt. to dependency management. > If you have nothing relevant to say, just don't say anything. > maybe you can come with a detailed description of your proposal's behavior, including how to manage case like this, instead of just throwing patch around ? If I do: # make CONFIG_WIRELESS_EXT=y allnoconfig I expect either a success or an error, not a silent discard. And *yes*, the problem already exists with "all*.config". Thanks, - Arnaud -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
