From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain/helpers: make sure we bail out when kernel headers check fails
Date: Tue, 19 Nov 2019 08:55:47 +0100 [thread overview]
Message-ID: <87d0dopaf0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20191113214114.GB26360@scaer> (Yann E. MORIN's message of "Wed, 13 Nov 2019 22:41:14 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
> On 2019-11-12 21:21 +0100, Thomas Petazzoni spake thusly:
>> In commit 6136765b23abd9faba610dd54ed276a777811575 ("toolchain:
>> generate check-headers program under $(BUILD_DIR)"), the
>> check_kernel_headers_version function was simplified to not check the
>> return value of the check-kernel-headers.sh script, assuming that
>> "make" does bail out on the first failing command.
>>
>> However, check_kernel_headers_version when used in $(2)_CONFIGURE_CMDS
>> from pkg-toolchain-external.mk, is called in a sequence of commands,
>> where the return value of each command is not checked. Therefore, a
>> failure of check-kernel-headers.sh no longer aborts the build.
>>
>> Since all other macros are using this principle of calling "exit 1",
>> we revert back to the same for check_kernel_headers_version, as it was
>> done prior to 6136765b23abd9faba610dd54ed276a777811575.
>>
>> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
>> Cc: Carlos Santos <unixmania@gmail.com>
> Applied to master, thanks.
Committed to 2019.02.x and 2019.08.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-11-19 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 20:21 [Buildroot] [PATCH] toolchain/helpers: make sure we bail out when kernel headers check fails Thomas Petazzoni
2019-11-12 21:21 ` Carlos Santos
2019-11-12 21:25 ` Thomas Petazzoni
2019-11-12 21:30 ` Carlos Santos
2019-11-13 21:41 ` Yann E. MORIN
2019-11-19 7:55 ` Peter Korsgaard [this message]
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=87d0dopaf0.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.