From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain/helpers: make sure we bail out when kernel headers check fails
Date: Tue, 12 Nov 2019 22:25:06 +0100 [thread overview]
Message-ID: <20191112222506.7630c00f@windsurf> (raw)
In-Reply-To: <CAJ4jsaeAhEVJY9pCR3-vhmhpuAndc3F1Y3GVjrM-KXbEJv34KQ@mail.gmail.com>
On Tue, 12 Nov 2019 18:21:15 -0300
Carlos Santos <unixmania@gmail.com> wrote:
> > diff --git a/toolchain/helpers.mk b/toolchain/helpers.mk
> > index 42e5522060..996cc70d44 100644
> > --- a/toolchain/helpers.mk
> > +++ b/toolchain/helpers.mk
> > @@ -163,7 +163,9 @@ copy_toolchain_sysroot = \
> > # $3: kernel version string, in the form: X.Y
> > #
> > check_kernel_headers_version = \
> > - support/scripts/check-kernel-headers.sh $(1) $(2) $(3)
> > + if ! support/scripts/check-kernel-headers.sh $(1) $(2) $(3); then \
> > + exit 1; \
> > + fi
> >
> > #
> > # Check the specific gcc version actually matches the version in the
> > --
> > 2.23.0
> >
>
> The function became a one-liner after commit 6136765b23. Wouldn't it
> be simpler and more readable to run the script and test the result,
> both in linux-headers.mk and pkg-toolchain-external.mk?
Yes, we could certainly do that. The aim of my patch was really just to
get back to where we were before, to fix the immediate issue. This of
course doesn't mean we can't improve things further.
I'll let Peter/Arnout/Yann decide what they want to do (i.e apply my
patch as-is, or have a more elaborate version).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-12 21:25 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 [this message]
2019-11-12 21:30 ` Carlos Santos
2019-11-13 21:41 ` Yann E. MORIN
2019-11-19 7:55 ` Peter Korsgaard
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=20191112222506.7630c00f@windsurf \
--to=thomas.petazzoni@bootlin.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.