LKML Archive on
help / color / mirror / Atom feed
From: Randy Dunlap <>
Cc: Randy Dunlap <>,
	Masahiro Yamada <>,
	Michal Marek <>,
Subject: [PATCH] kbuild: allow "make" targets 'versioncheck' and 'includecheck' withoug .config file
Date: Wed, 11 Aug 2021 15:54:42 -0700	[thread overview]
Message-ID: <> (raw)

Top-level Makefile targets 'versioncheck' and 'includecheck' don't
need a configured kernel (i.e., don't need a .config file), so add
them the the list of "no-dot-config-targets".
This eliminates the 'make' error:

*** Configuration file ".config" not found!
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
Makefile:759: include/config/auto.conf.cmd: No such file or directory

Signed-off-by: Randy Dunlap <>
Cc: Masahiro Yamada <>
Cc: Michal Marek <>
Fixes: I couldn't determine this.

 Makefile |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

--- linux-next-20210811.orig/Makefile
+++ linux-next-20210811/Makefile
@@ -274,7 +274,8 @@ no-dot-config-targets := $(clean-targets
 			 cscope gtags TAGS tags help% %docs check% coccicheck \
 			 $(version_h) headers headers_% archheaders archscripts \
 			 %asm-generic kernelversion %src-pkg dt_binding_check \
-			 outputmakefile rustfmt rustfmtcheck
+			 outputmakefile rustfmt rustfmtcheck \
+			 versioncheck includecheck
 # Installation targets should not require compiler. Unfortunately, vdso_install
 # is an exception where build artifacts may be updated. This must be fixed.
 no-compiler-targets := $(no-dot-config-targets) install dtbs_install \

             reply	other threads:[~2021-08-11 22:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 22:54 Randy Dunlap [this message]
2021-08-13  7:27 ` [PATCH] kbuild: allow "make" targets 'versioncheck' and 'includecheck' withoug .config file Masahiro Yamada
2021-08-13  8:32 ` Nicolas Schier
2021-08-13 15:00   ` Randy Dunlap

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).