From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Masahiro Yamada <masahiroy@kernel.org>
Subject: [PATCH 6/6] kbuild: check Make version
Date: Sat, 19 Nov 2022 04:53:07 +0900 [thread overview]
Message-ID: <20221118195307.86049-7-masahiroy@kernel.org> (raw)
In-Reply-To: <20221118195307.86049-1-masahiroy@kernel.org>
This is implemented based on test-le. It will work until GNU Make 10
is released.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
---
Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Makefile b/Makefile
index 93e5749ace55..979363590bd7 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
prev parent reply other threads:[~2022-11-18 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 19:53 [PATCH 0/6] kbuild: strive to avoid $(shell ...) invocations Masahiro Yamada
2022-11-18 19:53 ` [PATCH 1/6] kbuild: add test-{le,ge,lt,gt} macros Masahiro Yamada
2022-11-18 21:07 ` Masahiro Yamada
2022-11-18 19:53 ` [PATCH 2/6] kbuild: make CONFIG_*_VERSION always 6-digit Masahiro Yamada
2022-11-23 15:05 ` Masahiro Yamada
2022-11-18 19:53 ` [PATCH 3/6] kbuild: implement {gcc,clang}-min-version only with built-in functions Masahiro Yamada
2022-11-18 19:53 ` [PATCH 4/6] kbuild: add read-file macro Masahiro Yamada
2022-11-18 19:53 ` [PATCH 5/6] kconfig: refactor Makefile to reduce process forks Masahiro Yamada
2022-11-18 19:53 ` Masahiro Yamada [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=20221118195307.86049-7-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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