kernel-yocto: propagate configuration errors to bbclass
As pointed out by klapperichpaul@johndeere.com, missing configuration fragments were being picked up twice, once by the tools and once by the bbclass. Unfortunately, the tools error message was being detected as configs, and hence no error was reported at all. Rather than catching the output of the tools, we can instead check the return code and propagate the error message from the tools directly to the user. [YOCTO #11649] (From OE-Core rev: 3470a3839577b99322c10f830cdaa61128ef6b16) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> (cherry picked from commit 960652416e2390337df6d9734375d6829ceb6420) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
0ffe27ffef
commit
912d9f531e
|
@ -281,7 +281,8 @@ do_kernel_configme() {
|
||||||
|
|
||||||
meta_dir=$(kgit --meta)
|
meta_dir=$(kgit --meta)
|
||||||
configs="$(scc --configs -o ${meta_dir})"
|
configs="$(scc --configs -o ${meta_dir})"
|
||||||
if [ -z "${configs}" ]; then
|
if [ $? -ne 0 ]; then
|
||||||
|
bberror "${configs}"
|
||||||
bbfatal_log "Could not find configuration queue (${meta_dir}/config.queue)"
|
bbfatal_log "Could not find configuration queue (${meta_dir}/config.queue)"
|
||||||
fi
|
fi
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue