Keith Owens writes:
> There is no difference in autoconf.h between a suppressed variable
> (CONFIG_DEP="", no reference in autoconf) and a variable that is
> visible but set to n (CONFIG_DEP="n", explicitly undefined). In both
> cases the variable is undefined. C code cannot distinguish between
On Sat, 13 Apr 2002 11:04:35 -0500,
Michael Elizabeth Chastain <[EMAIL PROTECTED]> wrote:
>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 c
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
split-include is causing extra recompiles which AFAICT are unnecessary.
This applies to both kbuild 2.4 and 2.5.
Start with mrproper and a minimal .config, in particular
# CONFIG_DEBUG_KERNEL is not set
and no dependent kernel debug variables appear in .config.
yes '' | make oldconfig dep vmli
