Anton Altaparmakov <[EMAIL PROTECTED]>:
> </me ignorant of current state of cml2>I sometimes configure and compile
> kernels for different computers on my athlon due to the extremely fast
> compile time on the athlon. The autoprober would interfere here extremely
> badly. Is it disabled by default? I.e. if I do make menuconfig or make
> oldconfig will the autoprober temper with my choices?
Absolutely not.
To invoke the autoconfigurator, you do one of two things:
`make autoconfigure'
This runs the autoconfigurator in standalone mode. This gives you
an entire configuration, ready to build with.
`make autoprobe {config,menuconfig,xconfig}'
This runs the autoconfigurator in probe mode, which gives you
a report on facilities found (without making assumptions about facilities
not found). This report gets fed to your interactive configurator, which
then proceeds not to bother you with questions for which the autoprobe
report already gave it answers.
The ordinary make {config,menuconfig,xconfig} behaves as it always did.
--
<a href="http://www.tuxedo.org/~esr/";>Eric S. Raymond</a>
If we believe absurdities, we shall commit atrocities.
-- Voltaire
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
