[kaos] > On the one hand, new config entries default to 'n' (in .config, but > not config.out) so forgetting to make *config should be fail safe.
Not always. Remember when CONFIG_PSMOUSE went from tristate to bool late in 2.1.x? If you had CONFIG_PSMOUSE=m at that point you would get an unexpected kernel, if it would even build at all. > On the gripping hand, people who "know" that the patch has no affect > on their config will complain if they are forced to make *config. The same could be said for header files. Hey, all I did was reformat a couple of comments, why should I have to recompile all those C files? I think it's entirely reasonable to expect those who patch or edit Config.in files to rerun 'make oldconfig'. > The question is whether it should look for changes and should it > issue a warning and continue or insist that make *config be run. IMHO, insist. Let the user override with NO_MAKEFILE_GEN or whatever. Peter _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
