Keith Owens writes: > IMHO, split-include needs to recognise the first time that a variable > is seen (no previous split config file) and the variable is 'n'. For > this case, split-include should not create the file, i.e. treat it as > if the variable was still suppressed.
That assumes that all C code behaves the same on CONFIG_DEP="" and CONFIG_DEP="n". Formally that is not true, because "#ifdef CONFIG_DEP" will behave differently. A quick grep of the kernel source: grep -r '#.*if.*def.*CONFIG_' ... finds 10,000 such lines! Although most of them are booleans that will never have a value of "". Michael C _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
