[Buildroot] [PATCH 04/28] linux: use the defconfig mechanism after tuning the config

Peter Korsgaard jacmet at uclibc.org
Thu Jul 7 21:46:18 UTC 2011


>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at free-electrons.com> writes:

 Thomas> Currently, the kernel configuration mechanism works as follows for
 Thomas> custom configuration files:

 Thomas>  * Copy the custom config file to buildroot_defconfig in the kernel
 Thomas>    tree
 Thomas>  * Run "make buildroot_defconfig"
 Thomas>  * Remove the buildroot_defconfig
 Thomas>  * Tune the .config depending on some Buildroot options (EABI, MDEV,
 Thomas>    etc.)
 Thomas>  * Run oldconfig

 Thomas> And for a defconfig-based configuration:

 Thomas>  * Run "make XXX_defconfig"
 Thomas>  * Tune the .config depending on some Buildroot options (EABI, MDEV,
 Thomas>    etc.)
 Thomas>  * Run oldconfig

 Thomas> The problem is that the tuning done on the .config file can lead to
 Thomas> have new options available for which no value has been set. Therefore,
 Thomas> the "oldconfig" at the end of the process will hang the build process,
 Thomas> waiting for the user to confirm what should be done.

Why don't we just call 'make silentoldconfig' instead?

-- 
Bye, Peter Korsgaard



More information about the buildroot mailing list