On Sun, Sep 26, 2004 at 12:34:53AM +0200, Shaul Karl wrote: > I get the following: > > $ grep .config CONFIG_BROKEN > CONFIG_BROKEN_ON_SMP=y > $ > > Isn't CONFIG_BROKEN (without any suffix) supposed to be there too?
Not necessarily. I'm guessing that since it depends on !CLEAN_COMPILE,
you don't see it.
config BROKEN
bool
depends on !CLEAN_COMPILE
default y
config BROKEN_ON_SMP
bool
depends on BROKEN || !SMP
default y
> Am I
> right that the meaning of CONFIG_BROKEN* is only a warning that code
> that depends on it doesn't compile cleanly?
No. It means that the code is broken in some way. Doesn't compile is
one way, uses a kernel API in a way that is guarnateed to be wrong is
another, has blatant bugs is another.
> What is the relation
> between CONFIG_CLEAN_COMPILE and CONFIG_BROKEN*?
See above, or take a look at init/Kconfig.
Cheers,
Muli
--
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/
signature.asc
Description: Digital signature
