<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 29, 2019 at 11:02 AM Flavio Suligoi <<a href="mailto:f.suligoi@asem.it">f.suligoi@asem.it</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Bruce,<br>
<br>
> Sometimes, for example in case of missed dependecies, after the<br>
> execution of:<br>
> <br>
> merge_config.sh<br>
> <br>
> the resulting file ".config" can be empty.<br>
> This is the reason why is necessary test it and, in case, display<br>
> the "Could not configure ..." error message.<br>
> <br>
> This doesn't belong here. Auditing of the final .config is done in a separate task, and we could pickup that issue there.<br>
> <br>
> That being said, there are already checks for inputs that could result in something like this. How were you triggering this issue ? I'd like to reproduce it here, and perhaps come up with a different solution.<br>
> <br>
> Bruce<br>
<br>
I encountered this problem of the empty .config when I integrated <br>
the kernel 4.19 in my custom meta-layer based on a poky "rocko" (2.4) version.<br>
<br>
The kernel 4.19 requires the following dependencies in the kernel recipe:<br>
<br>
do_kernel_configme[depends] += "virtual/${TARGET_PREFIX}binutils:do_populate_sysroot"<br>
do_kernel_configme[depends] += "virtual/${TARGET_PREFIX}gcc:do_populate_sysroot"<br>
do_kernel_configme[depends] += "bc-native:do_populate_sysroot bison-native:do_populate_sysroot"<br>
<br>
(in the thud version of poky these dependencies are already integrated in the<br>
kernel-yocto.bbclass, but not in rocko)<br>
<br>
Without these dependencies the merge_config.sh fails without any error messages,<br>
the distro build process proceeds, but the built kernel is completely wrong<br>
(no modules and only default config).<br>
<br></blockquote><div><br></div><div><div class="gmail_default" style="font-size:small">Thanks for the info. I'll poke around a bit, and either queue these directly or do something</div><div class="gmail_default" style="font-size:small">similar in the kconfig audit step.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Cheers,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Bruce</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
For this reason I added the additional error log:<br>
<br>
${meta_dir}/cfg/merge_config_build-errors.log<br>
<br>
and the check for the empty .config<br>
<br>
Flavio<br>
<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end<br>- "Use the force Harry" - Gandalf, Star Trek II<br><br></div></div>