bb-kernel icon indicating copy to clipboard operation
bb-kernel copied to clipboard

Quick kernel rebuild after changing .config file

Open giuliomoro opened this issue 8 years ago • 4 comments

I am experimenting with some modules being built into the kernel or as loadable modules. The only way I manage to avoid linking errors after changing the config file is to run the build_kernel.sh command again, which cleans all the existing object files and therefore the build takes long.

Is there a quicker way to rebuild the kernel when changing the config file?

giuliomoro avatar Nov 29 '16 03:11 giuliomoro

There is: ;)

./tools/rebuild.sh

Regards,

RobertCNelson avatar Nov 29 '16 03:11 RobertCNelson

Thanks, that's what I usually use, but I see that if, e.g.: I change a module from "y" to "m", I get a linker error when using ./tools/rebuild.sh

giuliomoro avatar Nov 29 '16 03:11 giuliomoro

Oh, that just sounds like bad luck as you triggered a bug in the specific module. Kernel developers run random_defconfig from time to time, but they don't catch every possibility..

Regards,

RobertCNelson avatar Nov 29 '16 03:11 RobertCNelson

alas, is there any quick fix for these cases? For instance, when I disable SND_SOC I then get

drivers/built-in.o: In function `nxp_hdmi_codec_remove':
:(.text+0x5aa2c): undefined reference to `snd_soc_unregister_codec'
drivers/built-in.o: In function `nxp_hdmi_codec_probe':
:(.text+0x5aa42): undefined reference to `snd_soc_register_codec'

giuliomoro avatar Nov 29 '16 04:11 giuliomoro