jeff millar <[EMAIL PROTECTED]>:
> I sent this to Eric privately with a lot of data, but maybe someone else can
> jump in with an opinion about they way make oldconfig _should_ work.
>
> Several items...
>
> 1. Make oldconfig doesn't behave like cml1. With cml1, we would patch the
> kernel or copy in a backup .config file and run make oldconfig. It would do
> its thing for 30 seconds and be done...no (or few) questions asked. With
> CML2, I get an endless series of questions about each possible configuration
> item...much like "make config" does.
>
> I just want make oldconfig to get ready for make dep with the minimum of
> fuss. It's ok to ask about new configuration items but not a bunch of stuff
> already set.
I'm confused about this and would like some guidance. I have tried to make
oldconfig behave the way it is "supposed" to, but it may be that I don't
properly understand how it should behave.
What it does right now is load your config frozen, so the questions you
previously answered should not be asked again. Is that correct, or are
there nuances I'm missing?
--
<a href="http://www.tuxedo.org/~esr/";>Eric S. Raymond</a>
Americans have the will to resist because you have weapons.
If you don't have a gun, freedom of speech has no power.
-- Yoshimi Ishikawa, Japanese author, in the LA Times 15 Oct 1992
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
