On Thu, 2011-08-11 at 10:58 +0200, Michal Marek wrote: > I would much rather see include/config/auto.conf reset all configuration > variables to match what kconfig computed. I.e. use 'undefine CONFIG_FOO' > instead of '# CONFIG_FOO is not set'. That would be cute, but I'm not sure how to undefine something set on the command line: $ cat > Makefile <<EOF undefine BAR foo: echo $(BAR) EOF $ make foo BAR=hh echo hh hh Arguably, if someone *does* try something like Arnaud's "make CONFIG_FOO_BAR=y oldconfig bzImage" .. and it *wasn't* able to set CONFIG_FOO_BAR, then the nicest behaviour would be to fail, rather than to attempt to build it. So perhaps we should clean up only those settings inherited from the environment, and still (as in the patch I sent earlier) refuse to allow build targets in conjunction with CONFIG overrides on the command line? -- dwmw2 -- 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
