From: Bruce Ashfield Date: Tue, 13 Jun 2017 07:26:17 +0000 (-0400) Subject: kernel-yocto: propagate configuration errors to bbclass X-Git-Tag: uninative-1.7~163 X-Git-Url: https://code.ossystems.io/gitweb?a=commitdiff_plain;h=960652416e2390337df6d9734375d6829ceb6420;p=openembedded-core.git 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] Signed-off-by: Bruce Ashfield Signed-off-by: Ross Burton --- diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass index 50226f6d49..1ca0756c49 100644 --- a/meta/classes/kernel-yocto.bbclass +++ b/meta/classes/kernel-yocto.bbclass @@ -281,7 +281,8 @@ do_kernel_configme() { meta_dir=$(kgit --meta) 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)" fi