From: Nicolas Schier <nicolas@fjasle.eu>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH v2 5/5] kbuild: check Make version
Date: Thu, 24 Nov 2022 08:08:10 +0100 [thread overview]
Message-ID: <Y38YWrlPTpB7LoIY@bergen.fjasle.eu> (raw)
In-Reply-To: <Y36OZVnAZBqxcrBw@bergen.fjasle.eu>
[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]
On Wed 23 Nov 2022 22:19:33 GMT, Nicolas Schier wrote:
> On Thu 24 Nov 2022 00:18:28 GMT, Masahiro Yamada wrote:
> > This is implemented based on test-le. It will work until GNU Make 10
> > is released.
>
> ... and as long as nobody uses make versions w/ minor version numbers,
> cp. patch 3/5.
>
I had a wrong understanding of the ASCII sort and forgot to re-check my
own assumptions.
Thanks for that whole patch set!
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
>
> >
> > Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> > ---
> >
> > (no changes since v1)
> >
> > Makefile | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/Makefile b/Makefile
> > index 60ce9dcafc72..797fafbc1b45 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -368,6 +368,9 @@ else # !mixed-build
> >
> > include $(srctree)/scripts/Kbuild.include
> >
> > +# Check for the minimal Make version
> > +$(if $(call test-lt, $(MAKE_VERSION), 3.82), $(error Make $(MAKE_VERSION) is too old))
> > +
> > # Read KERNELRELEASE from include/config/kernel.release (if it exists)
> > KERNELRELEASE = $(call read-file, include/config/kernel.release)
> > KERNELVERSION = $(VERSION)$(if $(PATCHLEVEL),.$(PATCHLEVEL)$(if $(SUBLEVEL),.$(SUBLEVEL)))$(EXTRAVERSION)
> > --
> > 2.34.1
>
> --
> epost|xmpp: nicolas@fjasle.eu irc://oftc.net/nsc
> ↳ gpg: 18ed 52db e34f 860e e9fb c82b 7d97 0932 55a0 ce7f
> -- frykten for herren er opphav til kunnskap --
--
epost|xmpp: nicolas@fjasle.eu irc://oftc.net/nsc
↳ gpg: 18ed 52db e34f 860e e9fb c82b 7d97 0932 55a0 ce7f
-- frykten for herren er opphav til kunnskap --
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-24 7:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 15:18 [PATCH v2 1/5] kbuild: add test-{le,ge,lt,gt} macros Masahiro Yamada
2022-11-23 15:18 ` [PATCH v2 2/5] kbuild: implement {gcc,clang}-min-version only with built-in functions Masahiro Yamada
2022-11-23 20:37 ` Nicolas Schier
2022-11-23 21:17 ` Masahiro Yamada
2022-11-23 15:18 ` [PATCH v2 3/5] kbuild: add read-file macro Masahiro Yamada
2022-11-23 21:01 ` Nicolas Schier
2022-11-23 21:52 ` Masahiro Yamada
2022-11-24 4:45 ` Nicolas Schier
2022-11-23 15:18 ` [PATCH v2 4/5] kconfig: refactor Makefile to reduce process forks Masahiro Yamada
2022-11-23 21:14 ` Nicolas Schier
2022-11-23 15:18 ` [PATCH v2 5/5] kbuild: check Make version Masahiro Yamada
2022-11-23 21:19 ` Nicolas Schier
2022-11-24 7:08 ` Nicolas Schier [this message]
2022-11-23 20:05 ` [PATCH v2 1/5] kbuild: add test-{le,ge,lt,gt} macros Nicolas Schier
2022-12-02 17:56 ` Palmer Dabbelt
2022-12-08 1:42 ` Masahiro Yamada
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=Y38YWrlPTpB7LoIY@bergen.fjasle.eu \
--to=nicolas@fjasle.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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