From: Mark Brown <broonie@kernel.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kbuild@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Guillaume Tucker <guillaume.tucker@collabora.com>
Subject: [PATCH] merge_config.sh: Check error codes from make
Date: Thu, 8 Aug 2019 23:27:05 +0100 [thread overview]
Message-ID: <20190808222705.35973-1-broonie@kernel.org> (raw)
When we execute make after merging the configurations we ignore any
errors it produces causing whatever is running merge_config.sh to be
unaware of any failures. This issue was noticed by Guillaume Tucker
while looking at problems with testing of clang only builds in KernelCI
which caused Kbuild to be unable to find a working host compiler.
Reported-by: Guillaume Tucker <guillaume.tucker@collabora.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
scripts/kconfig/merge_config.sh | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/scripts/kconfig/merge_config.sh b/scripts/kconfig/merge_config.sh
index d924c51d28b7..96e960dce968 100755
--- a/scripts/kconfig/merge_config.sh
+++ b/scripts/kconfig/merge_config.sh
@@ -14,9 +14,10 @@
# Copyright 2011 Linaro
clean_up() {
+ RET=$1
rm -f $TMP_FILE
rm -f $MERGE_FILE
- exit
+ exit ${RET}
}
trap clean_up HUP INT TERM
@@ -171,6 +172,10 @@ fi
# alldefconfig: Fills in any missing symbols with Kconfig default
# allnoconfig: Fills in any missing symbols with # CONFIG_* is not set
make KCONFIG_ALLCONFIG=$TMP_FILE $OUTPUT_ARG $ALLTARGET
+RET=$?
+if [ "$RET" != "0" ]; then
+ clean_up $RET
+fi
# Check all specified config values took (might have missed-dependency issues)
--
2.20.1
next reply other threads:[~2019-08-08 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 22:27 Mark Brown [this message]
2019-08-10 9:11 ` [PATCH] merge_config.sh: Check error codes from make Masahiro Yamada
2019-08-12 10:43 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190808222705.35973-1-broonie@kernel.org \
--to=broonie@kernel.org \
--cc=guillaume.tucker@collabora.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox