License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 14:07:57 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2019-01-07 01:08:20 +00:00
|
|
|
VERSION = 5
|
2020-06-14 19:45:04 +00:00
|
|
|
PATCHLEVEL = 8
|
2011-05-30 00:43:36 +00:00
|
|
|
SUBLEVEL = 0
|
2020-06-28 22:00:24 +00:00
|
|
|
EXTRAVERSION = -rc3
|
2019-10-27 17:19:19 +00:00
|
|
|
NAME = Kleptomaniac Octopus
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# *DOCUMENTATION*
|
|
|
|
|
# To see a list of typical targets execute "make help"
|
|
|
|
|
# More info can be located in ./README
|
|
|
|
|
# Comments in this file are targeted only to the developer, do not
|
|
|
|
|
# expect to learn how to build the kernel reading this file.
|
|
|
|
|
|
2020-05-11 03:50:13 +00:00
|
|
|
$(if $(filter __%, $(MAKECMDGOALS)), \
|
|
|
|
|
$(error targets prefixed with '__' are only for internal use))
|
|
|
|
|
|
2017-10-04 03:56:05 +00:00
|
|
|
# That's our default target when none is given on the command line
|
2020-05-11 03:50:13 +00:00
|
|
|
PHONY := __all
|
|
|
|
|
__all:
|
2017-10-04 03:56:05 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# We are using a recursive build, so we need to do a little thinking
|
|
|
|
|
# to get the ordering right.
|
|
|
|
|
#
|
|
|
|
|
# Most importantly: sub-Makefiles should only ever modify files in
|
|
|
|
|
# their own directory. If in some directory we have a dependency on
|
|
|
|
|
# a file in another dir (which doesn't happen often, but it's often
|
2018-02-10 14:25:04 +00:00
|
|
|
# unavoidable when linking the built-in.a targets which finally
|
2005-04-16 22:20:36 +00:00
|
|
|
# turn into vmlinux), we will call a sub make in that other dir, and
|
|
|
|
|
# after that we are sure that everything which is in that other dir
|
|
|
|
|
# is now up to date.
|
|
|
|
|
#
|
|
|
|
|
# The only cases where we need to modify files which have global
|
|
|
|
|
# effects are thus separated out and done before the recursive
|
|
|
|
|
# descending is started. They are now explicitly listed as the
|
|
|
|
|
# prepare rule.
|
|
|
|
|
|
2019-03-26 04:02:19 +00:00
|
|
|
ifneq ($(sub_make_done),1)
|
2019-02-22 07:40:07 +00:00
|
|
|
|
|
|
|
|
# Do not use make's built-in rules and variables
|
|
|
|
|
# (this increases performance and avoids hard-to-debug behaviour)
|
|
|
|
|
MAKEFLAGS += -rR
|
|
|
|
|
|
|
|
|
|
# Avoid funny character set dependencies
|
|
|
|
|
unexport LC_ALL
|
|
|
|
|
LC_COLLATE=C
|
|
|
|
|
LC_NUMERIC=C
|
|
|
|
|
export LC_COLLATE LC_NUMERIC
|
|
|
|
|
|
|
|
|
|
# Avoid interference with shell env settings
|
|
|
|
|
unexport GREP_OPTIONS
|
|
|
|
|
|
2014-07-04 12:29:30 +00:00
|
|
|
# Beautify output
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
#
|
|
|
|
|
# Normally, we echo the whole command before executing it. By making
|
|
|
|
|
# that echo $($(quiet)$(cmd)), we now have the possibility to set
|
|
|
|
|
# $(quiet) to choose other forms of output instead, e.g.
|
|
|
|
|
#
|
|
|
|
|
# quiet_cmd_cc_o_c = Compiling $(RELDIR)/$@
|
|
|
|
|
# cmd_cc_o_c = $(CC) $(c_flags) -c -o $@ $<
|
|
|
|
|
#
|
|
|
|
|
# If $(quiet) is empty, the whole command will be printed.
|
|
|
|
|
# If it is set to "quiet_", only the short version will be printed.
|
|
|
|
|
# If it is set to "silent_", nothing will be printed at all, since
|
|
|
|
|
# the variable $(silent_cmd_cc_o_c) doesn't exist.
|
|
|
|
|
#
|
|
|
|
|
# A simple variant is to prefix commands with $(Q) - that's useful
|
|
|
|
|
# for commands that shall be hidden in non-verbose mode.
|
|
|
|
|
#
|
|
|
|
|
# $(Q)ln $@ :<
|
|
|
|
|
#
|
|
|
|
|
# If KBUILD_VERBOSE equals 0 then the above command will be hidden.
|
|
|
|
|
# If KBUILD_VERBOSE equals 1 then the above command is displayed.
|
2020-02-13 04:40:57 +00:00
|
|
|
# If KBUILD_VERBOSE equals 2 then give the reason why each target is rebuilt.
|
2014-07-04 12:29:30 +00:00
|
|
|
#
|
2005-04-16 22:20:36 +00:00
|
|
|
# To put more focus on warnings, be less verbose as default
|
|
|
|
|
# Use 'make V=1' to see the full commands
|
|
|
|
|
|
2009-05-26 08:03:07 +00:00
|
|
|
ifeq ("$(origin V)", "command line")
|
|
|
|
|
KBUILD_VERBOSE = $(V)
|
2005-04-16 22:20:36 +00:00
|
|
|
endif
|
|
|
|
|
ifndef KBUILD_VERBOSE
|
|
|
|
|
KBUILD_VERBOSE = 0
|
|
|
|
|
endif
|
|
|
|
|
|
2014-07-04 12:29:30 +00:00
|
|
|
ifeq ($(KBUILD_VERBOSE),1)
|
|
|
|
|
quiet =
|
|
|
|
|
Q =
|
|
|
|
|
else
|
|
|
|
|
quiet=quiet_
|
|
|
|
|
Q = @
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# If the user is running make -s (silent mode), suppress echoing of
|
|
|
|
|
# commands
|
|
|
|
|
|
2017-05-19 11:42:30 +00:00
|
|
|
ifneq ($(findstring s,$(filter-out --%,$(MAKEFLAGS))),)
|
2014-07-04 12:29:30 +00:00
|
|
|
quiet=silent_
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
export quiet Q KBUILD_VERBOSE
|
|
|
|
|
|
2019-03-30 12:04:14 +00:00
|
|
|
# Kbuild will save output files in the current working directory.
|
|
|
|
|
# This does not need to match to the root of the kernel source tree.
|
|
|
|
|
#
|
|
|
|
|
# For example, you can do this:
|
|
|
|
|
#
|
|
|
|
|
# cd /dir/to/store/output/files; make -f /dir/to/kernel/source/Makefile
|
|
|
|
|
#
|
|
|
|
|
# If you want to save output files in a different location, there are
|
|
|
|
|
# two syntaxes to specify it.
|
|
|
|
|
#
|
2005-04-16 22:20:36 +00:00
|
|
|
# 1) O=
|
|
|
|
|
# Use "make O=dir/to/store/output/files/"
|
2006-06-24 22:07:55 +00:00
|
|
|
#
|
2005-04-16 22:20:36 +00:00
|
|
|
# 2) Set KBUILD_OUTPUT
|
2019-03-30 12:04:14 +00:00
|
|
|
# Set the environment variable KBUILD_OUTPUT to point to the output directory.
|
|
|
|
|
# export KBUILD_OUTPUT=dir/to/store/output/files/; make
|
2005-04-16 22:20:36 +00:00
|
|
|
#
|
|
|
|
|
# The O= assignment takes precedence over the KBUILD_OUTPUT environment
|
|
|
|
|
# variable.
|
|
|
|
|
|
2019-03-30 12:04:14 +00:00
|
|
|
# Do we want to change the working directory?
|
2009-05-26 08:03:07 +00:00
|
|
|
ifeq ("$(origin O)", "command line")
|
|
|
|
|
KBUILD_OUTPUT := $(O)
|
2005-04-16 22:20:36 +00:00
|
|
|
endif
|
|
|
|
|
|
2019-03-30 12:04:14 +00:00
|
|
|
ifneq ($(KBUILD_OUTPUT),)
|
|
|
|
|
# Make's built-in functions such as $(abspath ...), $(realpath ...) cannot
|
|
|
|
|
# expand a shell special character '~'. We use a somewhat tedious way here.
|
|
|
|
|
abs_objtree := $(shell mkdir -p $(KBUILD_OUTPUT) && cd $(KBUILD_OUTPUT) && pwd)
|
|
|
|
|
$(if $(abs_objtree),, \
|
|
|
|
|
$(error failed to create output directory "$(KBUILD_OUTPUT)"))
|
|
|
|
|
|
|
|
|
|
# $(realpath ...) resolves symlinks
|
|
|
|
|
abs_objtree := $(realpath $(abs_objtree))
|
|
|
|
|
else
|
|
|
|
|
abs_objtree := $(CURDIR)
|
|
|
|
|
endif # ifneq ($(KBUILD_OUTPUT),)
|
|
|
|
|
|
|
|
|
|
ifeq ($(abs_objtree),$(CURDIR))
|
|
|
|
|
# Suppress "Entering directory ..." unless we are changing the work directory.
|
|
|
|
|
MAKEFLAGS += --no-print-directory
|
|
|
|
|
else
|
|
|
|
|
need-sub-make := 1
|
2016-04-02 19:38:53 +00:00
|
|
|
endif
|
|
|
|
|
|
2019-03-30 12:04:14 +00:00
|
|
|
abs_srctree := $(realpath $(dir $(lastword $(MAKEFILE_LIST))))
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-03-30 12:04:14 +00:00
|
|
|
ifneq ($(words $(subst :, ,$(abs_srctree))), 1)
|
|
|
|
|
$(error source directory cannot contain spaces or colons)
|
|
|
|
|
endif
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-03-30 12:04:14 +00:00
|
|
|
ifneq ($(abs_srctree),$(abs_objtree))
|
2018-09-14 06:33:23 +00:00
|
|
|
# Look for make include files relative to root of kernel src
|
|
|
|
|
#
|
|
|
|
|
# This does not become effective immediately because MAKEFLAGS is re-parsed
|
2019-03-30 12:04:14 +00:00
|
|
|
# once after the Makefile is read. We need to invoke sub-make.
|
|
|
|
|
MAKEFLAGS += --include-dir=$(abs_srctree)
|
2019-03-19 04:02:36 +00:00
|
|
|
need-sub-make := 1
|
2019-03-30 12:04:14 +00:00
|
|
|
endif
|
2019-02-22 07:40:07 +00:00
|
|
|
|
2020-05-11 03:50:12 +00:00
|
|
|
this-makefile := $(lastword $(MAKEFILE_LIST))
|
|
|
|
|
|
2019-03-19 04:02:36 +00:00
|
|
|
ifneq ($(filter 3.%,$(MAKE_VERSION)),)
|
|
|
|
|
# 'MAKEFLAGS += -rR' does not immediately become effective for GNU Make 3.x
|
|
|
|
|
# We need to invoke sub-make to avoid implicit rules in the top Makefile.
|
|
|
|
|
need-sub-make := 1
|
|
|
|
|
# Cancel implicit rules for this Makefile.
|
2020-05-11 03:50:12 +00:00
|
|
|
$(this-makefile): ;
|
2019-03-19 04:02:36 +00:00
|
|
|
endif
|
|
|
|
|
|
2019-03-30 12:04:14 +00:00
|
|
|
export abs_srctree abs_objtree
|
2019-03-26 04:02:19 +00:00
|
|
|
export sub_make_done := 1
|
|
|
|
|
|
2019-03-19 04:02:36 +00:00
|
|
|
ifeq ($(need-sub-make),1)
|
|
|
|
|
|
2020-05-11 03:50:13 +00:00
|
|
|
PHONY += $(MAKECMDGOALS) __sub-make
|
2007-09-21 23:09:02 +00:00
|
|
|
|
2020-05-11 03:50:13 +00:00
|
|
|
$(filter-out $(this-makefile), $(MAKECMDGOALS)) __all: __sub-make
|
2012-10-15 12:49:12 +00:00
|
|
|
@:
|
2007-09-21 23:09:02 +00:00
|
|
|
|
2017-06-30 02:45:43 +00:00
|
|
|
# Invoke a second make in the output directory, passing relevant variables
|
2020-05-11 03:50:13 +00:00
|
|
|
__sub-make:
|
2019-03-30 12:04:14 +00:00
|
|
|
$(Q)$(MAKE) -C $(abs_objtree) -f $(abs_srctree)/Makefile $(MAKECMDGOALS)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-03-19 04:02:36 +00:00
|
|
|
endif # need-sub-make
|
2019-03-26 04:02:19 +00:00
|
|
|
endif # sub_make_done
|
2019-03-19 04:02:36 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# We process the rest of the Makefile if this is the final invocation of make
|
2019-03-19 04:02:36 +00:00
|
|
|
ifeq ($(need-sub-make),)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2014-09-09 11:02:22 +00:00
|
|
|
# Do not print "Entering directory ...",
|
|
|
|
|
# but we want to display it when entering to the output directory
|
|
|
|
|
# so that IDEs/editors are able to understand relative filenames.
|
|
|
|
|
MAKEFLAGS += --no-print-directory
|
|
|
|
|
|
2014-09-09 11:02:24 +00:00
|
|
|
# Call a source code checker (by default, "sparse") as part of the
|
|
|
|
|
# C compilation.
|
|
|
|
|
#
|
|
|
|
|
# Use 'make C=1' to enable checking of only re-compiled files.
|
|
|
|
|
# Use 'make C=2' to enable checking of *all* source files, regardless
|
|
|
|
|
# of whether they are re-compiled or not.
|
|
|
|
|
#
|
2017-03-24 09:03:17 +00:00
|
|
|
# See the file "Documentation/dev-tools/sparse.rst" for more details,
|
|
|
|
|
# including where to get the "sparse" utility.
|
2014-09-09 11:02:24 +00:00
|
|
|
|
|
|
|
|
ifeq ("$(origin C)", "command line")
|
|
|
|
|
KBUILD_CHECKSRC = $(C)
|
|
|
|
|
endif
|
|
|
|
|
ifndef KBUILD_CHECKSRC
|
|
|
|
|
KBUILD_CHECKSRC = 0
|
|
|
|
|
endif
|
|
|
|
|
|
2019-09-21 07:05:41 +00:00
|
|
|
# Use make M=dir or set the environment variable KBUILD_EXTMOD to specify the
|
|
|
|
|
# directory of external module to build. Setting M= takes precedence.
|
2014-09-09 11:02:24 +00:00
|
|
|
ifeq ("$(origin M)", "command line")
|
|
|
|
|
KBUILD_EXTMOD := $(M)
|
|
|
|
|
endif
|
|
|
|
|
|
2020-05-24 15:42:15 +00:00
|
|
|
$(if $(word 2, $(KBUILD_EXTMOD)), \
|
|
|
|
|
$(error building multiple external modules is not supported))
|
|
|
|
|
|
2019-07-06 03:07:12 +00:00
|
|
|
export KBUILD_CHECKSRC KBUILD_EXTMOD
|
|
|
|
|
|
kbuild: make single targets work more correctly
Currently, the single target build directly descends into the directory
of the target. For example,
$ make foo/bar/baz.o
... directly descends into foo/bar/.
On the other hand, the normal build usually descends one directory at
a time, i.e. descends into foo/, and then foo/bar/.
This difference causes some problems.
[1] miss subdir-asflags-y, subdir-ccflags-y in upper Makefiles
The options in subdir-{as,cc}flags-y take effect in the current
and its sub-directories. In other words, they are inherited
downward. In the example above, the single target will miss
subdir-{as,cc}flags-y if they are defined in foo/Makefile.
[2] could be built in a different directory
As Documentation/kbuild/modules.rst section 4.3 says, Kbuild can
handle files that are spread over several sub-directories.
The build rule of foo/bar/baz.o may not necessarily be specified in
foo/bar/Makefile. It might be specifies in foo/Makefile as follows:
[foo/Makefile]
obj-y := bar/baz.o
This often happens when a module is so big that its source files
are divided into sub-directories.
In this case, there is no Makefile in the foo/bar/ directory, yet
the single target descends into foo/bar/, then fails due to the
missing Makefile. You can still do 'make foo/bar/' for partial
building, but cannot do 'make foo/bar/baz.s'. I believe the single
target '%.s' is a useful feature for inspecting the compiler output.
Some modules work around this issue by putting an empty Makefile
in every sub-directory.
This commit fixes those problems by making the single target build
descend in the same way as the normal build does.
Another change is the single target build will observe the CONFIG
options. Previously, it allowed users to build the foo.o even when
the corresponding CONFIG_FOO is disabled:
obj-$(CONFIG_FOO) += foo.o
In the new behavior, the single target build will just fail and show
"No rule to make target ..." (or "Nothing to be done for ..." if the
stale object already exists, but cannot be updated).
The disadvantage of this commit is the build speed. Now that the
single target build visits every directory and parses lots of
Makefiles, it is slower than before. (But, I hope it will not be
too slow.)
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-08-14 15:19:18 +00:00
|
|
|
extmod-prefix = $(if $(KBUILD_EXTMOD),$(KBUILD_EXTMOD)/)
|
|
|
|
|
|
2019-03-30 12:04:14 +00:00
|
|
|
ifeq ($(abs_srctree),$(abs_objtree))
|
2014-04-25 21:25:18 +00:00
|
|
|
# building in the source tree
|
|
|
|
|
srctree := .
|
2019-07-06 03:07:12 +00:00
|
|
|
building_out_of_srctree :=
|
2014-04-25 21:25:18 +00:00
|
|
|
else
|
2019-03-30 12:04:14 +00:00
|
|
|
ifeq ($(abs_srctree)/,$(dir $(abs_objtree)))
|
2014-04-25 21:25:18 +00:00
|
|
|
# building in a subdirectory of the source tree
|
|
|
|
|
srctree := ..
|
|
|
|
|
else
|
2019-03-30 12:04:14 +00:00
|
|
|
srctree := $(abs_srctree)
|
2014-04-25 21:25:18 +00:00
|
|
|
endif
|
2019-07-06 03:07:12 +00:00
|
|
|
building_out_of_srctree := 1
|
2014-04-25 21:25:18 +00:00
|
|
|
endif
|
2017-10-04 03:56:06 +00:00
|
|
|
|
2019-07-06 03:07:13 +00:00
|
|
|
ifneq ($(KBUILD_ABS_SRCTREE),)
|
|
|
|
|
srctree := $(abs_srctree)
|
|
|
|
|
endif
|
2017-10-04 03:56:06 +00:00
|
|
|
|
2014-04-25 15:29:45 +00:00
|
|
|
objtree := .
|
2019-02-22 07:40:09 +00:00
|
|
|
VPATH := $(srctree)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-07-06 03:07:12 +00:00
|
|
|
export building_out_of_srctree srctree objtree VPATH
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2017-10-04 03:56:06 +00:00
|
|
|
# To make sure we do not include .config for any of the *config targets
|
|
|
|
|
# catch them early, and hand them over to scripts/kconfig/Makefile
|
|
|
|
|
# It is allowed to specify more targets when calling make, including
|
|
|
|
|
# mixing *config targets and build targets.
|
|
|
|
|
# For example 'make oldconfig all'.
|
|
|
|
|
# Detect when mixed targets is specified, and make a second invocation
|
|
|
|
|
# of make so .config is not included in this case either (for *config).
|
|
|
|
|
|
|
|
|
|
version_h := include/generated/uapi/linux/version.h
|
|
|
|
|
old_version_h := include/linux/version.h
|
|
|
|
|
|
2018-02-11 08:40:29 +00:00
|
|
|
clean-targets := %clean mrproper cleandocs
|
|
|
|
|
no-dot-config-targets := $(clean-targets) \
|
2017-10-04 03:56:06 +00:00
|
|
|
cscope gtags TAGS tags help% %docs check% coccicheck \
|
kbuild: add 'headers' target to build up uapi headers in usr/include
In Linux build system, build targets and installation targets are
separated.
Examples are:
- 'make vmlinux' -> 'make install'
- 'make modules' -> 'make modules_install'
- 'make dtbs' -> 'make dtbs_install'
- 'make vdso' -> 'make vdso_install'
The intention is to run the build targets under the normal privilege,
then the installation targets under the root privilege since we need
the write permission to the system directories.
We have 'make headers_install' but the corresponding 'make headers'
stage does not exist. The purpose of headers_install is to provide
the kernel interface to C library. So, nobody would try to install
headers to /usr/include directly.
If 'sudo make INSTALL_HDR_PATH=/usr/include headers_install' were run,
some build artifacts in the kernel tree would be owned by root because
some of uapi headers are generated by 'uapi-asm-generic', 'archheaders'
targets.
Anyway, I believe it makes sense to split the header installation into
two stages.
[1] 'make headers'
Process headers in uapi directories by scripts/headers_install.sh
and copy them to usr/include
[2] 'make headers_install'
Copy '*.h' verbatim from usr/include to $(INSTALL_HDR_PATH)/include
For the backward compatibility, 'headers_install' depends on 'headers'.
Some samples expect uapi headers in usr/include. So, the 'headers'
target is useful to build up them in the fixed location usr/include
irrespective of INSTALL_HDR_PATH.
Another benefit is to stop polluting the final destination with the
time-stamp files '.install' and '.check'. Maybe you can see them in
your toolchains.
Lastly, my main motivation is to prepare for compile-testing uapi
headers. To build something, we have to save an object and .*.cmd
somewhere. The usr/include/ will be the work directory for that.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-06-04 10:14:02 +00:00
|
|
|
$(version_h) headers headers_% archheaders archscripts \
|
2020-03-26 19:29:33 +00:00
|
|
|
%asm-generic kernelversion %src-pkg dt_binding_check \
|
|
|
|
|
outputmakefile
|
2018-07-20 07:46:35 +00:00
|
|
|
no-sync-config-targets := $(no-dot-config-targets) install %install \
|
|
|
|
|
kernelrelease
|
kbuild: make single targets work more correctly
Currently, the single target build directly descends into the directory
of the target. For example,
$ make foo/bar/baz.o
... directly descends into foo/bar/.
On the other hand, the normal build usually descends one directory at
a time, i.e. descends into foo/, and then foo/bar/.
This difference causes some problems.
[1] miss subdir-asflags-y, subdir-ccflags-y in upper Makefiles
The options in subdir-{as,cc}flags-y take effect in the current
and its sub-directories. In other words, they are inherited
downward. In the example above, the single target will miss
subdir-{as,cc}flags-y if they are defined in foo/Makefile.
[2] could be built in a different directory
As Documentation/kbuild/modules.rst section 4.3 says, Kbuild can
handle files that are spread over several sub-directories.
The build rule of foo/bar/baz.o may not necessarily be specified in
foo/bar/Makefile. It might be specifies in foo/Makefile as follows:
[foo/Makefile]
obj-y := bar/baz.o
This often happens when a module is so big that its source files
are divided into sub-directories.
In this case, there is no Makefile in the foo/bar/ directory, yet
the single target descends into foo/bar/, then fails due to the
missing Makefile. You can still do 'make foo/bar/' for partial
building, but cannot do 'make foo/bar/baz.s'. I believe the single
target '%.s' is a useful feature for inspecting the compiler output.
Some modules work around this issue by putting an empty Makefile
in every sub-directory.
This commit fixes those problems by making the single target build
descend in the same way as the normal build does.
Another change is the single target build will observe the CONFIG
options. Previously, it allowed users to build the foo.o even when
the corresponding CONFIG_FOO is disabled:
obj-$(CONFIG_FOO) += foo.o
In the new behavior, the single target build will just fail and show
"No rule to make target ..." (or "Nothing to be done for ..." if the
stale object already exists, but cannot be updated).
The disadvantage of this commit is the build speed. Now that the
single target build visits every directory and parses lots of
Makefiles, it is slower than before. (But, I hope it will not be
too slow.)
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-08-14 15:19:18 +00:00
|
|
|
single-targets := %.a %.i %.ko %.lds %.ll %.lst %.mod %.o %.s %.symtypes %/
|
2017-10-04 03:56:06 +00:00
|
|
|
|
2019-08-10 15:53:03 +00:00
|
|
|
config-build :=
|
|
|
|
|
mixed-build :=
|
|
|
|
|
need-config := 1
|
|
|
|
|
may-sync-config := 1
|
kbuild: make single targets work more correctly
Currently, the single target build directly descends into the directory
of the target. For example,
$ make foo/bar/baz.o
... directly descends into foo/bar/.
On the other hand, the normal build usually descends one directory at
a time, i.e. descends into foo/, and then foo/bar/.
This difference causes some problems.
[1] miss subdir-asflags-y, subdir-ccflags-y in upper Makefiles
The options in subdir-{as,cc}flags-y take effect in the current
and its sub-directories. In other words, they are inherited
downward. In the example above, the single target will miss
subdir-{as,cc}flags-y if they are defined in foo/Makefile.
[2] could be built in a different directory
As Documentation/kbuild/modules.rst section 4.3 says, Kbuild can
handle files that are spread over several sub-directories.
The build rule of foo/bar/baz.o may not necessarily be specified in
foo/bar/Makefile. It might be specifies in foo/Makefile as follows:
[foo/Makefile]
obj-y := bar/baz.o
This often happens when a module is so big that its source files
are divided into sub-directories.
In this case, there is no Makefile in the foo/bar/ directory, yet
the single target descends into foo/bar/, then fails due to the
missing Makefile. You can still do 'make foo/bar/' for partial
building, but cannot do 'make foo/bar/baz.s'. I believe the single
target '%.s' is a useful feature for inspecting the compiler output.
Some modules work around this issue by putting an empty Makefile
in every sub-directory.
This commit fixes those problems by making the single target build
descend in the same way as the normal build does.
Another change is the single target build will observe the CONFIG
options. Previously, it allowed users to build the foo.o even when
the corresponding CONFIG_FOO is disabled:
obj-$(CONFIG_FOO) += foo.o
In the new behavior, the single target build will just fail and show
"No rule to make target ..." (or "Nothing to be done for ..." if the
stale object already exists, but cannot be updated).
The disadvantage of this commit is the build speed. Now that the
single target build visits every directory and parses lots of
Makefiles, it is slower than before. (But, I hope it will not be
too slow.)
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-08-14 15:19:18 +00:00
|
|
|
single-build :=
|
2017-10-04 03:56:06 +00:00
|
|
|
|
|
|
|
|
ifneq ($(filter $(no-dot-config-targets), $(MAKECMDGOALS)),)
|
|
|
|
|
ifeq ($(filter-out $(no-dot-config-targets), $(MAKECMDGOALS)),)
|
2019-08-10 15:53:03 +00:00
|
|
|
need-config :=
|
2017-10-04 03:56:06 +00:00
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
kbuild: do not update config when running install targets
"make syncconfig" is automatically invoked when any of the following
happens:
- .config is updated
- any of Kconfig files is updated
- any of environment variables referenced in Kconfig is changed
Then, it updates configuration files such as include/config/auto.conf
include/generated/autoconf.h, etc.
Even install targets (install, modules_install, etc.) are no exception.
However, they should never ever modify the source tree. Install
targets are often run with root privileges. Once those configuration
files are owned by root, "make mrproper" would end up with permission
error.
Install targets should just copy things blindly. They should not care
whether the configuration is up-to-date or not. This makes more sense
because we are interested in the configuration that was used in the
previous kernel building.
This issue has existed since before, but rarely happened. I expect
more chance where people are hit by this; with the new Kconfig syntax
extension, the .config now contains the compiler information. If you
cross-compile the kernel with CROSS_COMPILE, but forget to pass it
for "make install", you meet "any of environment variables referenced
in Kconfig is changed" because $(CC) is referenced in Kconfig.
Another scenario is the compiler upgrade before the installation.
Install targets need the configuration. "make modules_install" refer
to CONFIG_MODULES etc. "make dtbs_install" also needs CONFIG_ARCH_*
to decide which dtb files to install. However, the auto-update of
the configuration files should be avoided. We already do this for
external modules.
Now, Make targets are categorized into 3 groups:
[1] Do not need the kernel configuration at all
help, coccicheck, headers_install etc.
[2] Need the latest kernel configuration
If new config options are added, Kconfig will show prompt to
ask user's selection.
Build targets such as vmlinux, in-kernel modules are the cases.
[3] Need the kernel configuration, but do not want to update it
Install targets except headers_install, and external modules
are the cases.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2018-07-20 07:46:34 +00:00
|
|
|
ifneq ($(filter $(no-sync-config-targets), $(MAKECMDGOALS)),)
|
|
|
|
|
ifeq ($(filter-out $(no-sync-config-targets), $(MAKECMDGOALS)),)
|
2019-08-10 15:53:03 +00:00
|
|
|
may-sync-config :=
|
kbuild: do not update config when running install targets
"make syncconfig" is automatically invoked when any of the following
happens:
- .config is updated
- any of Kconfig files is updated
- any of environment variables referenced in Kconfig is changed
Then, it updates configuration files such as include/config/auto.conf
include/generated/autoconf.h, etc.
Even install targets (install, modules_install, etc.) are no exception.
However, they should never ever modify the source tree. Install
targets are often run with root privileges. Once those configuration
files are owned by root, "make mrproper" would end up with permission
error.
Install targets should just copy things blindly. They should not care
whether the configuration is up-to-date or not. This makes more sense
because we are interested in the configuration that was used in the
previous kernel building.
This issue has existed since before, but rarely happened. I expect
more chance where people are hit by this; with the new Kconfig syntax
extension, the .config now contains the compiler information. If you
cross-compile the kernel with CROSS_COMPILE, but forget to pass it
for "make install", you meet "any of environment variables referenced
in Kconfig is changed" because $(CC) is referenced in Kconfig.
Another scenario is the compiler upgrade before the installation.
Install targets need the configuration. "make modules_install" refer
to CONFIG_MODULES etc. "make dtbs_install" also needs CONFIG_ARCH_*
to decide which dtb files to install. However, the auto-update of
the configuration files should be avoided. We already do this for
external modules.
Now, Make targets are categorized into 3 groups:
[1] Do not need the kernel configuration at all
help, coccicheck, headers_install etc.
[2] Need the latest kernel configuration
If new config options are added, Kconfig will show prompt to
ask user's selection.
Build targets such as vmlinux, in-kernel modules are the cases.
[3] Need the kernel configuration, but do not want to update it
Install targets except headers_install, and external modules
are the cases.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2018-07-20 07:46:34 +00:00
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
ifneq ($(KBUILD_EXTMOD),)
|
2019-08-10 15:53:03 +00:00
|
|
|
may-sync-config :=
|
kbuild: do not update config when running install targets
"make syncconfig" is automatically invoked when any of the following
happens:
- .config is updated
- any of Kconfig files is updated
- any of environment variables referenced in Kconfig is changed
Then, it updates configuration files such as include/config/auto.conf
include/generated/autoconf.h, etc.
Even install targets (install, modules_install, etc.) are no exception.
However, they should never ever modify the source tree. Install
targets are often run with root privileges. Once those configuration
files are owned by root, "make mrproper" would end up with permission
error.
Install targets should just copy things blindly. They should not care
whether the configuration is up-to-date or not. This makes more sense
because we are interested in the configuration that was used in the
previous kernel building.
This issue has existed since before, but rarely happened. I expect
more chance where people are hit by this; with the new Kconfig syntax
extension, the .config now contains the compiler information. If you
cross-compile the kernel with CROSS_COMPILE, but forget to pass it
for "make install", you meet "any of environment variables referenced
in Kconfig is changed" because $(CC) is referenced in Kconfig.
Another scenario is the compiler upgrade before the installation.
Install targets need the configuration. "make modules_install" refer
to CONFIG_MODULES etc. "make dtbs_install" also needs CONFIG_ARCH_*
to decide which dtb files to install. However, the auto-update of
the configuration files should be avoided. We already do this for
external modules.
Now, Make targets are categorized into 3 groups:
[1] Do not need the kernel configuration at all
help, coccicheck, headers_install etc.
[2] Need the latest kernel configuration
If new config options are added, Kconfig will show prompt to
ask user's selection.
Build targets such as vmlinux, in-kernel modules are the cases.
[3] Need the kernel configuration, but do not want to update it
Install targets except headers_install, and external modules
are the cases.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2018-07-20 07:46:34 +00:00
|
|
|
endif
|
|
|
|
|
|
2017-10-04 03:56:06 +00:00
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
|
|
|
|
ifneq ($(filter config %config,$(MAKECMDGOALS)),)
|
2019-08-10 15:53:03 +00:00
|
|
|
config-build := 1
|
2017-10-04 03:56:06 +00:00
|
|
|
ifneq ($(words $(MAKECMDGOALS)),1)
|
2019-08-10 15:53:03 +00:00
|
|
|
mixed-build := 1
|
2017-10-04 03:56:06 +00:00
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
endif
|
2018-02-11 08:40:29 +00:00
|
|
|
|
kbuild: make single targets work more correctly
Currently, the single target build directly descends into the directory
of the target. For example,
$ make foo/bar/baz.o
... directly descends into foo/bar/.
On the other hand, the normal build usually descends one directory at
a time, i.e. descends into foo/, and then foo/bar/.
This difference causes some problems.
[1] miss subdir-asflags-y, subdir-ccflags-y in upper Makefiles
The options in subdir-{as,cc}flags-y take effect in the current
and its sub-directories. In other words, they are inherited
downward. In the example above, the single target will miss
subdir-{as,cc}flags-y if they are defined in foo/Makefile.
[2] could be built in a different directory
As Documentation/kbuild/modules.rst section 4.3 says, Kbuild can
handle files that are spread over several sub-directories.
The build rule of foo/bar/baz.o may not necessarily be specified in
foo/bar/Makefile. It might be specifies in foo/Makefile as follows:
[foo/Makefile]
obj-y := bar/baz.o
This often happens when a module is so big that its source files
are divided into sub-directories.
In this case, there is no Makefile in the foo/bar/ directory, yet
the single target descends into foo/bar/, then fails due to the
missing Makefile. You can still do 'make foo/bar/' for partial
building, but cannot do 'make foo/bar/baz.s'. I believe the single
target '%.s' is a useful feature for inspecting the compiler output.
Some modules work around this issue by putting an empty Makefile
in every sub-directory.
This commit fixes those problems by making the single target build
descend in the same way as the normal build does.
Another change is the single target build will observe the CONFIG
options. Previously, it allowed users to build the foo.o even when
the corresponding CONFIG_FOO is disabled:
obj-$(CONFIG_FOO) += foo.o
In the new behavior, the single target build will just fail and show
"No rule to make target ..." (or "Nothing to be done for ..." if the
stale object already exists, but cannot be updated).
The disadvantage of this commit is the build speed. Now that the
single target build visits every directory and parses lots of
Makefiles, it is slower than before. (But, I hope it will not be
too slow.)
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-08-14 15:19:18 +00:00
|
|
|
# We cannot build single targets and the others at the same time
|
|
|
|
|
ifneq ($(filter $(single-targets), $(MAKECMDGOALS)),)
|
|
|
|
|
single-build := 1
|
|
|
|
|
ifneq ($(filter-out $(single-targets), $(MAKECMDGOALS)),)
|
|
|
|
|
mixed-build := 1
|
|
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
2018-02-11 08:40:29 +00:00
|
|
|
# For "make -j clean all", "make -j mrproper defconfig all", etc.
|
|
|
|
|
ifneq ($(filter $(clean-targets),$(MAKECMDGOALS)),)
|
|
|
|
|
ifneq ($(filter-out $(clean-targets),$(MAKECMDGOALS)),)
|
2019-08-10 15:53:03 +00:00
|
|
|
mixed-build := 1
|
2018-02-11 08:40:29 +00:00
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
2017-10-04 03:56:06 +00:00
|
|
|
# install and modules_install need also be processed one by one
|
|
|
|
|
ifneq ($(filter install,$(MAKECMDGOALS)),)
|
|
|
|
|
ifneq ($(filter modules_install,$(MAKECMDGOALS)),)
|
2019-08-10 15:53:03 +00:00
|
|
|
mixed-build := 1
|
2017-10-04 03:56:06 +00:00
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
2019-08-10 15:53:03 +00:00
|
|
|
ifdef mixed-build
|
2017-10-04 03:56:06 +00:00
|
|
|
# ===========================================================================
|
|
|
|
|
# We're called with mixed targets (*config and build targets).
|
|
|
|
|
# Handle them one by one.
|
|
|
|
|
|
|
|
|
|
PHONY += $(MAKECMDGOALS) __build_one_by_one
|
|
|
|
|
|
2020-05-11 03:50:13 +00:00
|
|
|
$(MAKECMDGOALS): __build_one_by_one
|
2017-10-04 03:56:06 +00:00
|
|
|
@:
|
|
|
|
|
|
|
|
|
|
__build_one_by_one:
|
|
|
|
|
$(Q)set -e; \
|
|
|
|
|
for i in $(MAKECMDGOALS); do \
|
|
|
|
|
$(MAKE) -f $(srctree)/Makefile $$i; \
|
|
|
|
|
done
|
|
|
|
|
|
2019-08-10 15:53:03 +00:00
|
|
|
else # !mixed-build
|
2017-10-04 03:56:06 +00:00
|
|
|
|
|
|
|
|
include scripts/Kbuild.include
|
|
|
|
|
|
|
|
|
|
# Read KERNELRELEASE from include/config/kernel.release (if it exists)
|
|
|
|
|
KERNELRELEASE = $(shell cat include/config/kernel.release 2> /dev/null)
|
|
|
|
|
KERNELVERSION = $(VERSION)$(if $(PATCHLEVEL),.$(PATCHLEVEL)$(if $(SUBLEVEL),.$(SUBLEVEL)))$(EXTRAVERSION)
|
|
|
|
|
export VERSION PATCHLEVEL SUBLEVEL KERNELRELEASE KERNELVERSION
|
|
|
|
|
|
2018-09-04 10:47:21 +00:00
|
|
|
include scripts/subarch.include
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# Cross compiling and selecting different set of gcc/bin-utils
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
#
|
|
|
|
|
# When performing cross compilation for other architectures ARCH shall be set
|
|
|
|
|
# to the target architecture. (See arch/* for the possibilities).
|
|
|
|
|
# ARCH can be set during invocation of make:
|
|
|
|
|
# make ARCH=ia64
|
|
|
|
|
# Another way is to have ARCH set in the environment.
|
|
|
|
|
# The default ARCH is the host where make is executed.
|
|
|
|
|
|
|
|
|
|
# CROSS_COMPILE specify the prefix used for all executables used
|
|
|
|
|
# during compilation. Only gcc and related bin-utils executables
|
|
|
|
|
# are prefixed with $(CROSS_COMPILE).
|
|
|
|
|
# CROSS_COMPILE can be set on the command line
|
|
|
|
|
# make CROSS_COMPILE=ia64-linux-
|
|
|
|
|
# Alternatively CROSS_COMPILE can be set in the environment.
|
|
|
|
|
# Default value for CROSS_COMPILE is not to prefix executables
|
|
|
|
|
# Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
|
2009-10-11 21:22:58 +00:00
|
|
|
ARCH ?= $(SUBARCH)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# Architecture as present in compile.h
|
2007-10-11 09:11:36 +00:00
|
|
|
UTS_MACHINE := $(ARCH)
|
|
|
|
|
SRCARCH := $(ARCH)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-11-12 19:14:19 +00:00
|
|
|
# Additional ARCH settings for x86
|
|
|
|
|
ifeq ($(ARCH),i386)
|
|
|
|
|
SRCARCH := x86
|
|
|
|
|
endif
|
|
|
|
|
ifeq ($(ARCH),x86_64)
|
|
|
|
|
SRCARCH := x86
|
|
|
|
|
endif
|
2007-10-25 17:42:04 +00:00
|
|
|
|
2008-12-03 07:17:12 +00:00
|
|
|
# Additional ARCH settings for sparc
|
2010-10-25 05:48:23 +00:00
|
|
|
ifeq ($(ARCH),sparc32)
|
|
|
|
|
SRCARCH := sparc
|
|
|
|
|
endif
|
2008-07-27 21:00:59 +00:00
|
|
|
ifeq ($(ARCH),sparc64)
|
2008-12-03 07:17:12 +00:00
|
|
|
SRCARCH := sparc
|
2008-07-27 21:00:59 +00:00
|
|
|
endif
|
2008-06-20 22:24:17 +00:00
|
|
|
|
2009-04-10 23:39:27 +00:00
|
|
|
# Additional ARCH settings for sh
|
|
|
|
|
ifeq ($(ARCH),sh64)
|
|
|
|
|
SRCARCH := sh
|
|
|
|
|
endif
|
|
|
|
|
|
2006-06-09 05:12:51 +00:00
|
|
|
KCONFIG_CONFIG ?= .config
|
2010-12-14 16:39:44 +00:00
|
|
|
export KCONFIG_CONFIG
|
2006-06-09 05:12:51 +00:00
|
|
|
|
kbuild: use KBUILD_DEFCONFIG as the fallback for DEFCONFIG_LIST
Most of the Kconfig commands (except defconfig and all*config) read
the .config file as a base set of CONFIG options.
When it does not exist, the files in DEFCONFIG_LIST are searched in
this order and loaded if found.
I do not see much sense in the last two lines in DEFCONFIG_LIST.
[1] ARCH_DEFCONFIG
The entry for DEFCONFIG_LIST is guarded by 'depends on !UML'. So, the
ARCH_DEFCONFIG definition in arch/x86/um/Kconfig is meaningless.
arch/{sh,sparc,x86}/Kconfig define ARCH_DEFCONFIG depending on 32 or
64 bit variant symbols. This is a little bit strange; ARCH_DEFCONFIG
should be a fixed string because the base config file is loaded before
the symbol evaluation stage.
Using KBUILD_DEFCONFIG makes more sense because it is fixed before
Kconfig is invoked. Fortunately, arch/{sh,sparc,x86}/Makefile define it
in the same way, and it works as expected. Hence, replace ARCH_DEFCONFIG
with "arch/$(SRCARCH)/configs/$(KBUILD_DEFCONFIG)".
[2] arch/$(ARCH)/defconfig
This file path is no longer valid. The defconfig files are always located
in the arch configs/ directories.
$ find arch -name defconfig | sort
arch/alpha/configs/defconfig
arch/arm64/configs/defconfig
arch/csky/configs/defconfig
arch/nds32/configs/defconfig
arch/riscv/configs/defconfig
arch/s390/configs/defconfig
arch/unicore32/configs/defconfig
The path arch/*/configs/defconfig is already covered by
"arch/$(SRCARCH)/configs/$(KBUILD_DEFCONFIG)". So, this file path is
not necessary.
I moved the default KBUILD_DEFCONFIG to the top Makefile. Otherwise,
the 7 architectures listed above would end up with endless loop of
syncconfig.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2020-02-28 03:46:40 +00:00
|
|
|
# Default file for 'make defconfig'. This may be overridden by arch-Makefile.
|
|
|
|
|
export KBUILD_DEFCONFIG := defconfig
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# SHELL used by kbuild
|
2019-08-25 13:28:37 +00:00
|
|
|
CONFIG_SHELL := sh
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-07-12 10:38:36 +00:00
|
|
|
HOST_LFS_CFLAGS := $(shell getconf LFS_CFLAGS 2>/dev/null)
|
|
|
|
|
HOST_LFS_LDFLAGS := $(shell getconf LFS_LDFLAGS 2>/dev/null)
|
|
|
|
|
HOST_LFS_LIBS := $(shell getconf LFS_LIBS 2>/dev/null)
|
2017-07-09 18:02:36 +00:00
|
|
|
|
2020-04-08 01:36:23 +00:00
|
|
|
ifneq ($(LLVM),)
|
|
|
|
|
HOSTCC = clang
|
|
|
|
|
HOSTCXX = clang++
|
|
|
|
|
else
|
|
|
|
|
HOSTCC = gcc
|
|
|
|
|
HOSTCXX = g++
|
|
|
|
|
endif
|
kbuild: add infrastructure to build userspace programs
Kbuild supports the infrastructure to build host programs, but there
was no support to build userspace programs for the target architecture
(i.e. the same architecture as the kernel).
Sam Ravnborg worked on this in 2014 (https://lkml.org/lkml/2014/7/13/154),
but it was not merged. One problem at that time was, there was no good way
to know whether $(CC) can link standalone programs. In fact, pre-built
kernel.org toolchains [1] are often used for building the kernel, but they
do not provide libc.
Now, we can handle this cleanly because the compiler capability is
evaluated at the Kconfig time. If $(CC) cannot link standalone programs,
the relevant options are hidden by 'depends on CC_CAN_LINK'.
The implementation just mimics scripts/Makefile.host
The userspace programs are compiled with the same flags as the host
programs. In addition, it uses -m32 or -m64 if it is found in
$(KBUILD_CFLAGS).
This new syntax has two usecases.
- Sample programs
Several userspace programs under samples/ include UAPI headers
installed in usr/include. Most of them were previously built for
the host architecture just to use the 'hostprogs' syntax.
However, 'make headers' always works for the target architecture.
This caused the arch mismatch in cross-compiling. To fix this
distortion, sample code should be built for the target architecture.
- Bpfilter
net/bpfilter/Makefile compiles bpfilter_umh as the user mode helper,
and embeds it into the kernel. Currently, it overrides HOSTCC with
CC to use the 'hostprogs' syntax. This hack should go away.
[1]: https://mirrors.edge.kernel.org/pub/tools/crosstool/
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
2020-04-29 03:45:14 +00:00
|
|
|
|
|
|
|
|
export KBUILD_USERCFLAGS := -Wall -Wmissing-prototypes -Wstrict-prototypes \
|
|
|
|
|
-O2 -fomit-frame-pointer -std=gnu89
|
|
|
|
|
export KBUILD_USERLDFLAGS :=
|
|
|
|
|
|
|
|
|
|
KBUILD_HOSTCFLAGS := $(KBUILD_USERCFLAGS) $(HOST_LFS_CFLAGS) $(HOSTCFLAGS)
|
kbuild: add -Wall to KBUILD_HOSTCXXFLAGS
Add -Wall to catch more warnings for C++ host programs.
When I submitted the previous version, the 0-day bot reported
-Wc++11-compat warnings for old GCC:
HOSTCXX -fPIC scripts/gcc-plugins/latent_entropy_plugin.o
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include/tm.h:28:0,
from scripts/gcc-plugins/gcc-common.h:15,
from scripts/gcc-plugins/latent_entropy_plugin.c:78:
/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include/config/elfos.h:102:21: warning: C++11 requires a space between string literal and macro [-Wc++11-compat]
fprintf ((FILE), "%s"HOST_WIDE_INT_PRINT_UNSIGNED"\n",\
^
/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include/config/elfos.h:170:24: warning: C++11 requires a space between string literal and macro [-Wc++11-compat]
fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n", \
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include/tm.h:42:0,
from scripts/gcc-plugins/gcc-common.h:15,
from scripts/gcc-plugins/latent_entropy_plugin.c:78:
/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include/defaults.h:126:24: warning: C++11 requires a space between string literal and macro [-Wc++11-compat]
fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n", \
^
The source of the warnings is in the plugin headers, so we have no
control of it. I just suppressed them by adding -Wno-c++11-compat to
scripts/gcc-plugins/Makefile.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Acked-by: Kees Cook <keescook@chromium.org>
2020-03-25 03:14:32 +00:00
|
|
|
KBUILD_HOSTCXXFLAGS := -Wall -O2 $(HOST_LFS_CFLAGS) $(HOSTCXXFLAGS)
|
2018-07-10 00:46:02 +00:00
|
|
|
KBUILD_HOSTLDFLAGS := $(HOST_LFS_LDFLAGS) $(HOSTLDFLAGS)
|
|
|
|
|
KBUILD_HOSTLDLIBS := $(HOST_LFS_LIBS) $(HOSTLDLIBS)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# Make variables (CC, etc...)
|
|
|
|
|
CPP = $(CC) -E
|
2020-04-08 01:36:23 +00:00
|
|
|
ifneq ($(LLVM),)
|
|
|
|
|
CC = clang
|
|
|
|
|
LD = ld.lld
|
|
|
|
|
AR = llvm-ar
|
|
|
|
|
NM = llvm-nm
|
|
|
|
|
OBJCOPY = llvm-objcopy
|
|
|
|
|
OBJDUMP = llvm-objdump
|
|
|
|
|
READELF = llvm-readelf
|
|
|
|
|
OBJSIZE = llvm-size
|
|
|
|
|
STRIP = llvm-strip
|
|
|
|
|
else
|
|
|
|
|
CC = $(CROSS_COMPILE)gcc
|
|
|
|
|
LD = $(CROSS_COMPILE)ld
|
2005-04-16 22:20:36 +00:00
|
|
|
AR = $(CROSS_COMPILE)ar
|
|
|
|
|
NM = $(CROSS_COMPILE)nm
|
|
|
|
|
OBJCOPY = $(CROSS_COMPILE)objcopy
|
|
|
|
|
OBJDUMP = $(CROSS_COMPILE)objdump
|
2019-12-04 22:54:41 +00:00
|
|
|
READELF = $(CROSS_COMPILE)readelf
|
2020-04-08 01:36:23 +00:00
|
|
|
OBJSIZE = $(CROSS_COMPILE)size
|
|
|
|
|
STRIP = $(CROSS_COMPILE)strip
|
|
|
|
|
endif
|
kbuild: add ability to generate BTF type info for vmlinux
This patch adds new config option to trigger generation of BTF type
information from DWARF debuginfo for vmlinux and kernel modules through
pahole, which in turn relies on libbpf for btf_dedup() algorithm.
The intent is to record compact type information of all types used
inside kernel, including all the structs/unions/typedefs/etc. This
enables BPF's compile-once-run-everywhere ([0]) approach, in which
tracing programs that are inspecting kernel's internal data (e.g.,
struct task_struct) can be compiled on a system running some kernel
version, but would be possible to run on other kernel versions (and
configurations) without recompilation, even if the layout of structs
changed and/or some of the fields were added, removed, or renamed.
This is only possible if BPF loader can get kernel type info to adjust
all the offsets correctly. This patch is a first time in this direction,
making sure that BTF type info is part of Linux kernel image in
non-loadable ELF section.
BTF deduplication ([1]) algorithm typically provides 100x savings
compared to DWARF data, so resulting .BTF section is not big as is
typically about 2MB in size.
[0] http://vger.kernel.org/lpc-bpf2018.html#session-2
[1] https://facebookmicrosites.github.io/bpf/blog/2018/11/14/btf-enhancement.html
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@fb.com>
Cc: Yonghong Song <yhs@fb.com>
Cc: Martin KaFai Lau <kafai@fb.com>
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
Acked-by: David S. Miller <davem@davemloft.net>
Acked-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
2019-04-02 16:49:50 +00:00
|
|
|
PAHOLE = pahole
|
2017-12-09 16:02:28 +00:00
|
|
|
LEX = flex
|
|
|
|
|
YACC = bison
|
2005-04-16 22:20:36 +00:00
|
|
|
AWK = awk
|
2009-07-20 19:37:11 +00:00
|
|
|
INSTALLKERNEL := installkernel
|
2005-04-16 22:20:36 +00:00
|
|
|
DEPMOD = /sbin/depmod
|
|
|
|
|
PERL = perl
|
2014-07-18 04:40:11 +00:00
|
|
|
PYTHON = python
|
kbuild: add PYTHON2 and PYTHON3 variables
The variable 'PYTHON' allows users to specify a proper executable
name in case the default 'python' does not work. However, this does
not address the case where both Python 2.x and 3.x scripts are used
in one source tree.
PEP 394 (https://www.python.org/dev/peps/pep-0394/) provides a
convention for Python scripts portability. Here is a quotation:
In order to tolerate differences across platforms, all new code
that needs to invoke the Python interpreter should not specify
'python', but rather should specify either 'python2' or 'python3'.
This distinction should be made in shebangs, when invoking from a
shell script, when invoking via the system() call, or when invoking
in any other context.
One exception to this is scripts that are deliberately written to
be source compatible with both Python 2.x and 3.x. Such scripts may
continue to use python on their shebang line without affecting their
portability.
To meet this requirement, this commit adds new variables 'PYTHON2'
and 'PYTHON3'.
arch/ia64/scripts/unwcheck.py is the only script that has ever used
$(PYTHON). Recent commit bd5edbe67794 ("ia64: convert unwcheck.py to
python3") converted it to be compatible with both Python 2.x and 3.x,
so this is the exceptional case where the use of 'python' is allowed.
So, I did not touch arch/ia64/Makefile.
tools/perf/Makefile.config sets PYTHON and PYTHON2 by itself, so it
is not affected by this commit.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2018-03-13 09:12:02 +00:00
|
|
|
PYTHON3 = python3
|
2005-04-16 22:20:36 +00:00
|
|
|
CHECK = sparse
|
2019-08-25 13:28:37 +00:00
|
|
|
BASH = bash
|
kbuild: fix broken builds because of GZIP,BZIP2,LZOP variables
Redefine GZIP, BZIP2, LZOP variables as KGZIP, KBZIP2, KLZOP resp.
GZIP, BZIP2, LZOP env variables are reserved by the tools. The original
attempt to redefine them internally doesn't work in makefiles/scripts
intercall scenarios, e.g., "make GZIP=gzip bindeb-pkg" and results in
broken builds. There can be other broken build commands because of this,
so the universal solution is to use non-reserved env variables for the
compression tools.
Fixes: 8dfb61dcbace ("kbuild: add variables for compression tools")
Signed-off-by: Denis Efremov <efremov@linux.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2020-06-08 09:59:44 +00:00
|
|
|
KGZIP = gzip
|
|
|
|
|
KBZIP2 = bzip2
|
|
|
|
|
KLZOP = lzop
|
kbuild: add variables for compression tools
Allow user to use alternative implementations of compression tools,
such as pigz, pbzip2, pxz. For example, multi-threaded tools to
speed up the build:
$ make GZIP=pigz BZIP2=pbzip2
Variables _GZIP, _BZIP2, _LZOP are used internally because original env
vars are reserved by the tools. The use of GZIP in gzip tool is obsolete
since 2015. However, alternative implementations (e.g., pigz) still rely
on it. BZIP2, BZIP, LZOP vars are not obsolescent.
The credit goes to @grsecurity.
As a sidenote, for multi-threaded lzma, xz compression one can use:
$ export XZ_OPT="--threads=0"
Signed-off-by: Denis Efremov <efremov@linux.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2020-06-05 07:39:55 +00:00
|
|
|
LZMA = lzma
|
|
|
|
|
LZ4 = lz4c
|
|
|
|
|
XZ = xz
|
|
|
|
|
|
2008-12-27 21:38:44 +00:00
|
|
|
CHECKFLAGS := -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ \
|
2018-02-15 21:07:50 +00:00
|
|
|
-Wbitwise -Wno-return-void -Wno-unknown-attribute $(CF)
|
2019-03-14 23:41:59 +00:00
|
|
|
NOSTDINC_FLAGS :=
|
kbuild: allow assignment to {A,C,LD}FLAGS_MODULE on the command line
It is now possible to assign options to AS, CC and LD
on the command line - which is only used when building modules.
{A,C,LD}FLAGS_MODULE was all used both in the top-level Makefile
in the arch makefiles, thus users had no way to specify
additional options to AS, CC, LD when building modules
without overriding the original value.
Introduce a new set of variables KBUILD_{A,C,LD}FLAGS_MODULE
that is used by arch specific files and free up
{A,C,LD}FLAGS_MODULE so they can be assigned on
the command line.
All arch Makefiles that used the old variables has been updated.
Note: Previously we had a MODFLAGS variable for both
AS and CC. But in favour of consistency this was dropped.
So in some cases arch Makefile has one assignmnet replaced by
two assignmnets.
Note2: MODFLAGS was not documented and is dropped
without any notice. I do not expect much/any breakage
from this.
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Cc: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Mike Frysinger <vapier@gentoo.org>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Chen Liqin <liqin.chen@sunplusct.com>
Acked-by: Mike Frysinger <vapier@gentoo.org> [blackfin]
Acked-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com> [avr32]
Signed-off-by: Michal Marek <mmarek@suse.cz>
2010-07-28 15:33:09 +00:00
|
|
|
CFLAGS_MODULE =
|
|
|
|
|
AFLAGS_MODULE =
|
|
|
|
|
LDFLAGS_MODULE =
|
2005-04-16 22:20:36 +00:00
|
|
|
CFLAGS_KERNEL =
|
|
|
|
|
AFLAGS_KERNEL =
|
2016-06-07 09:57:02 +00:00
|
|
|
LDFLAGS_vmlinux =
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2012-10-02 17:01:26 +00:00
|
|
|
# Use USERINCLUDE when you must reference the UAPI directories only.
|
|
|
|
|
USERINCLUDE := \
|
2017-10-04 03:56:04 +00:00
|
|
|
-I$(srctree)/arch/$(SRCARCH)/include/uapi \
|
|
|
|
|
-I$(objtree)/arch/$(SRCARCH)/include/generated/uapi \
|
2012-10-02 17:01:26 +00:00
|
|
|
-I$(srctree)/include/uapi \
|
2016-06-15 15:45:45 +00:00
|
|
|
-I$(objtree)/include/generated/uapi \
|
2012-10-02 17:01:26 +00:00
|
|
|
-include $(srctree)/include/linux/kconfig.h
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# Use LINUXINCLUDE when you must reference the include/ directory.
|
|
|
|
|
# Needed to be compatible with the O= option
|
2012-10-02 17:01:26 +00:00
|
|
|
LINUXINCLUDE := \
|
2017-10-04 03:56:04 +00:00
|
|
|
-I$(srctree)/arch/$(SRCARCH)/include \
|
|
|
|
|
-I$(objtree)/arch/$(SRCARCH)/include/generated \
|
2019-07-06 03:07:12 +00:00
|
|
|
$(if $(building_out_of_srctree),-I$(srctree)/include) \
|
2017-06-06 07:15:28 +00:00
|
|
|
-I$(objtree)/include \
|
|
|
|
|
$(USERINCLUDE)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-12-14 08:05:37 +00:00
|
|
|
KBUILD_AFLAGS := -D__ASSEMBLY__ -fno-PIE
|
2018-12-14 08:05:38 +00:00
|
|
|
KBUILD_CFLAGS := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs \
|
2018-12-14 08:05:37 +00:00
|
|
|
-fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE \
|
2019-03-04 12:55:20 +00:00
|
|
|
-Werror=implicit-function-declaration -Werror=implicit-int \
|
2014-10-20 09:23:12 +00:00
|
|
|
-Wno-format-security \
|
kbuild: do not call cc-option before KBUILD_CFLAGS initialization
Some $(call cc-option,...) are invoked very early, even before
KBUILD_CFLAGS, etc. are initialized.
The returned string from $(call cc-option,...) depends on
KBUILD_CPPFLAGS, KBUILD_CFLAGS, and GCC_PLUGINS_CFLAGS.
Since they are exported, they are not empty when the top Makefile
is recursively invoked.
The recursion occurs in several places. For example, the top
Makefile invokes itself for silentoldconfig. "make tinyconfig",
"make rpm-pkg" are the cases, too.
In those cases, the second call of cc-option from the same line
runs a different shell command due to non-pristine KBUILD_CFLAGS.
To get the same result all the time, KBUILD_* and GCC_PLUGINS_CFLAGS
must be initialized before any call of cc-option. This avoids
garbage data in the .cache.mk file.
Move all calls of cc-option below the config targets because target
compiler flags are unnecessary for Kconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
2017-10-12 09:22:25 +00:00
|
|
|
-std=gnu89
|
|
|
|
|
KBUILD_CPPFLAGS := -D__KERNEL__
|
2010-07-28 17:11:27 +00:00
|
|
|
KBUILD_AFLAGS_KERNEL :=
|
|
|
|
|
KBUILD_CFLAGS_KERNEL :=
|
kbuild: allow assignment to {A,C,LD}FLAGS_MODULE on the command line
It is now possible to assign options to AS, CC and LD
on the command line - which is only used when building modules.
{A,C,LD}FLAGS_MODULE was all used both in the top-level Makefile
in the arch makefiles, thus users had no way to specify
additional options to AS, CC, LD when building modules
without overriding the original value.
Introduce a new set of variables KBUILD_{A,C,LD}FLAGS_MODULE
that is used by arch specific files and free up
{A,C,LD}FLAGS_MODULE so they can be assigned on
the command line.
All arch Makefiles that used the old variables has been updated.
Note: Previously we had a MODFLAGS variable for both
AS and CC. But in favour of consistency this was dropped.
So in some cases arch Makefile has one assignmnet replaced by
two assignmnets.
Note2: MODFLAGS was not documented and is dropped
without any notice. I do not expect much/any breakage
from this.
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Cc: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Mike Frysinger <vapier@gentoo.org>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Chen Liqin <liqin.chen@sunplusct.com>
Acked-by: Mike Frysinger <vapier@gentoo.org> [blackfin]
Acked-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com> [avr32]
Signed-off-by: Michal Marek <mmarek@suse.cz>
2010-07-28 15:33:09 +00:00
|
|
|
KBUILD_AFLAGS_MODULE := -DMODULE
|
|
|
|
|
KBUILD_CFLAGS_MODULE := -DMODULE
|
2019-08-14 16:06:22 +00:00
|
|
|
KBUILD_LDFLAGS_MODULE :=
|
|
|
|
|
export KBUILD_LDS_MODULE := $(srctree)/scripts/module-common.lds
|
2018-08-23 23:20:39 +00:00
|
|
|
KBUILD_LDFLAGS :=
|
kbuild: do not call cc-option before KBUILD_CFLAGS initialization
Some $(call cc-option,...) are invoked very early, even before
KBUILD_CFLAGS, etc. are initialized.
The returned string from $(call cc-option,...) depends on
KBUILD_CPPFLAGS, KBUILD_CFLAGS, and GCC_PLUGINS_CFLAGS.
Since they are exported, they are not empty when the top Makefile
is recursively invoked.
The recursion occurs in several places. For example, the top
Makefile invokes itself for silentoldconfig. "make tinyconfig",
"make rpm-pkg" are the cases, too.
In those cases, the second call of cc-option from the same line
runs a different shell command due to non-pristine KBUILD_CFLAGS.
To get the same result all the time, KBUILD_* and GCC_PLUGINS_CFLAGS
must be initialized before any call of cc-option. This avoids
garbage data in the .cache.mk file.
Move all calls of cc-option below the config targets because target
compiler flags are unnecessary for Kconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
2017-10-12 09:22:25 +00:00
|
|
|
GCC_PLUGINS_CFLAGS :=
|
2019-07-29 09:15:17 +00:00
|
|
|
CLANG_FLAGS :=
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-03-26 05:57:18 +00:00
|
|
|
export ARCH SRCARCH CONFIG_SHELL BASH HOSTCC KBUILD_HOSTCFLAGS CROSS_COMPILE LD CC
|
2019-12-04 22:54:41 +00:00
|
|
|
export CPP AR NM STRIP OBJCOPY OBJDUMP OBJSIZE READELF PAHOLE LEX YACC AWK INSTALLKERNEL
|
2020-01-06 08:36:28 +00:00
|
|
|
export PERL PYTHON PYTHON3 CHECK CHECKFLAGS MAKE UTS_MACHINE HOSTCXX
|
kbuild: fix broken builds because of GZIP,BZIP2,LZOP variables
Redefine GZIP, BZIP2, LZOP variables as KGZIP, KBZIP2, KLZOP resp.
GZIP, BZIP2, LZOP env variables are reserved by the tools. The original
attempt to redefine them internally doesn't work in makefiles/scripts
intercall scenarios, e.g., "make GZIP=gzip bindeb-pkg" and results in
broken builds. There can be other broken build commands because of this,
so the universal solution is to use non-reserved env variables for the
compression tools.
Fixes: 8dfb61dcbace ("kbuild: add variables for compression tools")
Signed-off-by: Denis Efremov <efremov@linux.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2020-06-08 09:59:44 +00:00
|
|
|
export KGZIP KBZIP2 KLZOP LZMA LZ4 XZ
|
2019-01-21 12:54:39 +00:00
|
|
|
export KBUILD_HOSTCXXFLAGS KBUILD_HOSTLDFLAGS KBUILD_HOSTLDLIBS LDFLAGS_MODULE
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-08-23 23:20:39 +00:00
|
|
|
export KBUILD_CPPFLAGS NOSTDINC_FLAGS LINUXINCLUDE OBJCOPYFLAGS KBUILD_LDFLAGS
|
2018-02-06 23:36:00 +00:00
|
|
|
export KBUILD_CFLAGS CFLAGS_KERNEL CFLAGS_MODULE
|
2019-11-14 18:02:54 +00:00
|
|
|
export CFLAGS_KASAN CFLAGS_KASAN_NOSANITIZE CFLAGS_UBSAN CFLAGS_KCSAN
|
2007-10-15 19:59:31 +00:00
|
|
|
export KBUILD_AFLAGS AFLAGS_KERNEL AFLAGS_MODULE
|
kbuild: allow assignment to {A,C,LD}FLAGS_MODULE on the command line
It is now possible to assign options to AS, CC and LD
on the command line - which is only used when building modules.
{A,C,LD}FLAGS_MODULE was all used both in the top-level Makefile
in the arch makefiles, thus users had no way to specify
additional options to AS, CC, LD when building modules
without overriding the original value.
Introduce a new set of variables KBUILD_{A,C,LD}FLAGS_MODULE
that is used by arch specific files and free up
{A,C,LD}FLAGS_MODULE so they can be assigned on
the command line.
All arch Makefiles that used the old variables has been updated.
Note: Previously we had a MODFLAGS variable for both
AS and CC. But in favour of consistency this was dropped.
So in some cases arch Makefile has one assignmnet replaced by
two assignmnets.
Note2: MODFLAGS was not documented and is dropped
without any notice. I do not expect much/any breakage
from this.
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Cc: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Mike Frysinger <vapier@gentoo.org>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Chen Liqin <liqin.chen@sunplusct.com>
Acked-by: Mike Frysinger <vapier@gentoo.org> [blackfin]
Acked-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com> [avr32]
Signed-off-by: Michal Marek <mmarek@suse.cz>
2010-07-28 15:33:09 +00:00
|
|
|
export KBUILD_AFLAGS_MODULE KBUILD_CFLAGS_MODULE KBUILD_LDFLAGS_MODULE
|
2010-07-28 17:11:27 +00:00
|
|
|
export KBUILD_AFLAGS_KERNEL KBUILD_CFLAGS_KERNEL
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# Files to ignore in find ... statements
|
|
|
|
|
|
2014-02-06 12:51:42 +00:00
|
|
|
export RCS_FIND_IGNORE := \( -name SCCS -o -name BitKeeper -o -name .svn -o \
|
|
|
|
|
-name CVS -o -name .pc -o -name .hg -o -name .git \) \
|
|
|
|
|
-prune -o
|
2012-02-16 21:49:15 +00:00
|
|
|
export RCS_TAR_IGNORE := --exclude SCCS --exclude BitKeeper --exclude .svn \
|
|
|
|
|
--exclude CVS --exclude .pc --exclude .hg --exclude .git
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# ===========================================================================
|
|
|
|
|
# Rules shared between *config targets and build targets
|
|
|
|
|
|
2017-08-02 02:31:06 +00:00
|
|
|
# Basic helpers built in scripts/basic/
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += scripts_basic
|
2005-04-16 22:20:36 +00:00
|
|
|
scripts_basic:
|
|
|
|
|
$(Q)$(MAKE) $(build)=scripts/basic
|
2009-11-17 15:48:25 +00:00
|
|
|
$(Q)rm -f .tmp_quiet_recordmcount
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += outputmakefile
|
2019-08-22 04:46:11 +00:00
|
|
|
# Before starting out-of-tree build, make sure the source tree is clean.
|
2006-05-02 10:33:20 +00:00
|
|
|
# outputmakefile generates a Makefile in the output directory, if using a
|
|
|
|
|
# separate output directory. This allows convenient use of make in the
|
|
|
|
|
# output directory.
|
2019-02-03 08:48:40 +00:00
|
|
|
# At the same time when output Makefile generated, generate .gitignore to
|
|
|
|
|
# ignore whole output directory
|
2005-04-16 22:20:36 +00:00
|
|
|
outputmakefile:
|
2019-07-06 03:07:12 +00:00
|
|
|
ifdef building_out_of_srctree
|
2019-08-22 04:46:11 +00:00
|
|
|
$(Q)if [ -f $(srctree)/.config -o \
|
|
|
|
|
-d $(srctree)/include/config -o \
|
|
|
|
|
-d $(srctree)/arch/$(SRCARCH)/include/generated ]; then \
|
|
|
|
|
echo >&2 "***"; \
|
|
|
|
|
echo >&2 "*** The source tree is not clean, please run 'make$(if $(findstring command line, $(origin ARCH)), ARCH=$(ARCH)) mrproper'"; \
|
|
|
|
|
echo >&2 "*** in $(abs_srctree)";\
|
|
|
|
|
echo >&2 "***"; \
|
|
|
|
|
false; \
|
|
|
|
|
fi
|
2009-01-10 03:56:13 +00:00
|
|
|
$(Q)ln -fsn $(srctree) source
|
2018-09-18 08:45:53 +00:00
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/mkmakefile $(srctree)
|
2019-03-26 04:26:58 +00:00
|
|
|
$(Q)test -e .gitignore || \
|
|
|
|
|
{ echo "# this is build directory, ignore it"; echo "*"; } > .gitignore
|
2006-05-02 10:33:20 +00:00
|
|
|
endif
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-10-30 13:26:34 +00:00
|
|
|
ifneq ($(shell $(CC) --version 2>&1 | head -n 1 | grep clang),)
|
2017-11-07 19:46:13 +00:00
|
|
|
ifneq ($(CROSS_COMPILE),)
|
2019-07-29 09:15:17 +00:00
|
|
|
CLANG_FLAGS += --target=$(notdir $(CROSS_COMPILE:%-=%))
|
2019-02-11 19:30:04 +00:00
|
|
|
GCC_TOOLCHAIN_DIR := $(dir $(shell which $(CROSS_COMPILE)elfedit))
|
2018-11-06 03:04:55 +00:00
|
|
|
CLANG_FLAGS += --prefix=$(GCC_TOOLCHAIN_DIR)
|
2018-09-18 02:31:57 +00:00
|
|
|
GCC_TOOLCHAIN := $(realpath $(GCC_TOOLCHAIN_DIR)/..)
|
2017-11-07 19:46:13 +00:00
|
|
|
endif
|
|
|
|
|
ifneq ($(GCC_TOOLCHAIN),)
|
2018-11-06 03:04:55 +00:00
|
|
|
CLANG_FLAGS += --gcc-toolchain=$(GCC_TOOLCHAIN)
|
2017-11-07 19:46:13 +00:00
|
|
|
endif
|
2020-04-08 01:36:22 +00:00
|
|
|
ifneq ($(LLVM_IAS),1)
|
2018-11-06 03:04:55 +00:00
|
|
|
CLANG_FLAGS += -no-integrated-as
|
2019-06-27 19:14:48 +00:00
|
|
|
endif
|
kbuild: Add -Werror=unknown-warning-option to CLANG_FLAGS
In commit ebcc5928c5d9 ("arm64: Silence gcc warnings about arch ABI
drift"), the arm64 Makefile added -Wno-psabi to KBUILD_CFLAGS, which is
a GCC only option so clang rightfully complains:
warning: unknown warning option '-Wno-psabi' [-Wunknown-warning-option]
https://clang.llvm.org/docs/DiagnosticsReference.html#wunknown-warning-option
However, by default, this is merely a warning so the build happily goes
on with a slew of these warnings in the process.
Commit c3f0d0bc5b01 ("kbuild, LLVMLinux: Add -Werror to cc-option to
support clang") worked around this behavior in cc-option by adding
-Werror so that unknown flags cause an error. However, this all happens
silently and when an unknown flag is added to the build unconditionally
like -Wno-psabi, cc-option will always fail because there is always an
unknown flag in the list of flags. This manifested as link time failures
in the arm64 libstub because -fno-stack-protector didn't get added to
KBUILD_CFLAGS.
To avoid these weird cryptic failures in the future, make clang behave
like gcc and immediately error when it encounters an unknown flag by
adding -Werror=unknown-warning-option to CLANG_FLAGS. This can be added
unconditionally for clang because it is supported by at least 3.0.0,
according to godbolt [1] and 4.0.0, according to its documentation [2],
which is far earlier than we typically support.
[1]: https://godbolt.org/z/7F7rm3
[2]: https://releases.llvm.org/4.0.0/tools/clang/docs/DiagnosticsReference.html#wunknown-warning-option
Link: https://github.com/ClangBuiltLinux/linux/issues/511
Link: https://github.com/ClangBuiltLinux/linux/issues/517
Suggested-by: Peter Smith <peter.smith@linaro.org>
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
Tested-by: Nick Desaulniers <ndesaulniers@google.com>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-06-11 18:43:31 +00:00
|
|
|
CLANG_FLAGS += -Werror=unknown-warning-option
|
2018-11-06 03:04:55 +00:00
|
|
|
KBUILD_CFLAGS += $(CLANG_FLAGS)
|
|
|
|
|
KBUILD_AFLAGS += $(CLANG_FLAGS)
|
2018-11-12 04:21:15 +00:00
|
|
|
export CLANG_FLAGS
|
2017-11-07 19:46:13 +00:00
|
|
|
endif
|
|
|
|
|
|
kbuild: fix endless syncconfig in case arch Makefile sets CROSS_COMPILE
Commit 21c54b774744 ("kconfig: show compiler version text in the top
comment") was intended to detect the compiler upgrade, but Geert
reported a breakage on the m68k build.
The compiler upgrade is detected by the change of the environment
variable, CC_VERSION_TEXT, which contains the first line of the output
from $(CC) --version. Currently, this works well when CROSS_COMPILE
is given via the environment variable or the Make command line.
However, some architectures such as m68k can specify CROSS_COMPILE
from arch/$(SRCARCH)/Makefile as well. In this case, "make ARCH=m68k"
ends up with endless syncconfig loop.
$ make ARCH=m68k defconfig
*** Default configuration is based on 'multi_defconfig'
#
# configuration written to .config
#
$ make ARCH=m68k
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
Things are happening like this:
Because arch/$(SRCARCH)/Makefile is included after CC_VERSION_TEXT
is set, it contains the host compiler version in the defconfig phase.
To create or update auto.conf, the following line is triggered:
include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
$(Q)$(MAKE) -f $(srctree)/Makefile syncconfig
This recurses the top Makefile after arch/$(SRCARCH)/Makefile is
included. CROSS_COMPILE is set to a m68k toolchain prefix and
exported to the recursed Make. Then, syncconfig is invoked with
the target compiler version in CC_VERSION_TEXT.
The Make will restart because auto.conf and auto.conf.cmd have been
updated. At this point, CROSS_COMPILE is reset, so CC_VERSION_TEXT
is set to the host compiler version again. Then, syncconfig is
triggered due to the change of CC_VERSION_TEXT. This loop continues
eternally.
To fix this problem, $(CC_VERSION_TEXT) must be evaluated only after
arch/$(SRCARCH)/Makefile. Setting it earlier is OK as long as it is
defined by using the '=' operator instead of ':='.
For the defconfig phase, $(CC_VERSION_TEXT) is evaluated when Kbuild
descends into scripts/kconfig/, so it contains the target compiler
version correctly.
include/config/auto.conf.cmd references $(CC_VERSION_TEXT) as well,
so it must be included after arch/$(SRCARCH)/Makefile.
Fixes: 21c54b774744 ("kconfig: show compiler version text in the top comment")
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
2018-06-08 00:21:43 +00:00
|
|
|
# The expansion should be delayed until arch/$(SRCARCH)/Makefile is included.
|
|
|
|
|
# Some architectures define CROSS_COMPILE in arch/$(SRCARCH)/Makefile.
|
|
|
|
|
# CC_VERSION_TEXT is referenced from Kconfig (so it needs export),
|
|
|
|
|
# and from include/config/auto.conf.cmd to detect the compiler upgrade.
|
2019-05-09 07:35:55 +00:00
|
|
|
CC_VERSION_TEXT = $(shell $(CC) --version 2>/dev/null | head -n 1)
|
kbuild: fix endless syncconfig in case arch Makefile sets CROSS_COMPILE
Commit 21c54b774744 ("kconfig: show compiler version text in the top
comment") was intended to detect the compiler upgrade, but Geert
reported a breakage on the m68k build.
The compiler upgrade is detected by the change of the environment
variable, CC_VERSION_TEXT, which contains the first line of the output
from $(CC) --version. Currently, this works well when CROSS_COMPILE
is given via the environment variable or the Make command line.
However, some architectures such as m68k can specify CROSS_COMPILE
from arch/$(SRCARCH)/Makefile as well. In this case, "make ARCH=m68k"
ends up with endless syncconfig loop.
$ make ARCH=m68k defconfig
*** Default configuration is based on 'multi_defconfig'
#
# configuration written to .config
#
$ make ARCH=m68k
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
Things are happening like this:
Because arch/$(SRCARCH)/Makefile is included after CC_VERSION_TEXT
is set, it contains the host compiler version in the defconfig phase.
To create or update auto.conf, the following line is triggered:
include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
$(Q)$(MAKE) -f $(srctree)/Makefile syncconfig
This recurses the top Makefile after arch/$(SRCARCH)/Makefile is
included. CROSS_COMPILE is set to a m68k toolchain prefix and
exported to the recursed Make. Then, syncconfig is invoked with
the target compiler version in CC_VERSION_TEXT.
The Make will restart because auto.conf and auto.conf.cmd have been
updated. At this point, CROSS_COMPILE is reset, so CC_VERSION_TEXT
is set to the host compiler version again. Then, syncconfig is
triggered due to the change of CC_VERSION_TEXT. This loop continues
eternally.
To fix this problem, $(CC_VERSION_TEXT) must be evaluated only after
arch/$(SRCARCH)/Makefile. Setting it earlier is OK as long as it is
defined by using the '=' operator instead of ':='.
For the defconfig phase, $(CC_VERSION_TEXT) is evaluated when Kbuild
descends into scripts/kconfig/, so it contains the target compiler
version correctly.
include/config/auto.conf.cmd references $(CC_VERSION_TEXT) as well,
so it must be included after arch/$(SRCARCH)/Makefile.
Fixes: 21c54b774744 ("kconfig: show compiler version text in the top comment")
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
2018-06-08 00:21:43 +00:00
|
|
|
|
2019-08-10 15:53:03 +00:00
|
|
|
ifdef config-build
|
2005-04-16 22:20:36 +00:00
|
|
|
# ===========================================================================
|
|
|
|
|
# *config targets only - make sure prerequisites are updated, and descend
|
|
|
|
|
# in scripts/kconfig to make the *config target
|
|
|
|
|
|
|
|
|
|
# Read arch specific Makefile to set KBUILD_DEFCONFIG as needed.
|
|
|
|
|
# KBUILD_DEFCONFIG may point out an alternative default configuration
|
|
|
|
|
# used for 'make defconfig'
|
2015-03-27 11:43:36 +00:00
|
|
|
include arch/$(SRCARCH)/Makefile
|
kbuild: fix endless syncconfig in case arch Makefile sets CROSS_COMPILE
Commit 21c54b774744 ("kconfig: show compiler version text in the top
comment") was intended to detect the compiler upgrade, but Geert
reported a breakage on the m68k build.
The compiler upgrade is detected by the change of the environment
variable, CC_VERSION_TEXT, which contains the first line of the output
from $(CC) --version. Currently, this works well when CROSS_COMPILE
is given via the environment variable or the Make command line.
However, some architectures such as m68k can specify CROSS_COMPILE
from arch/$(SRCARCH)/Makefile as well. In this case, "make ARCH=m68k"
ends up with endless syncconfig loop.
$ make ARCH=m68k defconfig
*** Default configuration is based on 'multi_defconfig'
#
# configuration written to .config
#
$ make ARCH=m68k
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
Things are happening like this:
Because arch/$(SRCARCH)/Makefile is included after CC_VERSION_TEXT
is set, it contains the host compiler version in the defconfig phase.
To create or update auto.conf, the following line is triggered:
include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
$(Q)$(MAKE) -f $(srctree)/Makefile syncconfig
This recurses the top Makefile after arch/$(SRCARCH)/Makefile is
included. CROSS_COMPILE is set to a m68k toolchain prefix and
exported to the recursed Make. Then, syncconfig is invoked with
the target compiler version in CC_VERSION_TEXT.
The Make will restart because auto.conf and auto.conf.cmd have been
updated. At this point, CROSS_COMPILE is reset, so CC_VERSION_TEXT
is set to the host compiler version again. Then, syncconfig is
triggered due to the change of CC_VERSION_TEXT. This loop continues
eternally.
To fix this problem, $(CC_VERSION_TEXT) must be evaluated only after
arch/$(SRCARCH)/Makefile. Setting it earlier is OK as long as it is
defined by using the '=' operator instead of ':='.
For the defconfig phase, $(CC_VERSION_TEXT) is evaluated when Kbuild
descends into scripts/kconfig/, so it contains the target compiler
version correctly.
include/config/auto.conf.cmd references $(CC_VERSION_TEXT) as well,
so it must be included after arch/$(SRCARCH)/Makefile.
Fixes: 21c54b774744 ("kconfig: show compiler version text in the top comment")
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
2018-06-08 00:21:43 +00:00
|
|
|
export KBUILD_DEFCONFIG KBUILD_KCONFIG CC_VERSION_TEXT
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-08-22 04:46:13 +00:00
|
|
|
config: outputmakefile scripts_basic FORCE
|
2008-12-13 22:00:45 +00:00
|
|
|
$(Q)$(MAKE) $(build)=scripts/kconfig $@
|
|
|
|
|
|
2019-08-22 04:46:13 +00:00
|
|
|
%config: outputmakefile scripts_basic FORCE
|
2005-04-16 22:20:36 +00:00
|
|
|
$(Q)$(MAKE) $(build)=scripts/kconfig $@
|
|
|
|
|
|
2019-08-10 15:53:03 +00:00
|
|
|
else #!config-build
|
2005-04-16 22:20:36 +00:00
|
|
|
# ===========================================================================
|
|
|
|
|
# Build targets only - this includes vmlinux, arch specific targets, clean
|
|
|
|
|
# targets and others. In general all targets except *config targets.
|
|
|
|
|
|
2017-10-04 03:56:06 +00:00
|
|
|
# If building an external module we do not care about the all: rule
|
2020-05-11 03:50:13 +00:00
|
|
|
# but instead __all depend on modules
|
2017-10-04 03:56:06 +00:00
|
|
|
PHONY += all
|
|
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
2020-05-11 03:50:13 +00:00
|
|
|
__all: all
|
2017-10-04 03:56:06 +00:00
|
|
|
else
|
2020-05-11 03:50:13 +00:00
|
|
|
__all: modules
|
2017-10-04 03:56:06 +00:00
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# Decide whether to build built-in, modular, or both.
|
|
|
|
|
# Normally, just do built-in.
|
|
|
|
|
|
|
|
|
|
KBUILD_MODULES :=
|
|
|
|
|
KBUILD_BUILTIN := 1
|
|
|
|
|
|
|
|
|
|
# If we have only "make modules", don't compile built-in objects.
|
|
|
|
|
ifeq ($(MAKECMDGOALS),modules)
|
2020-05-31 08:47:06 +00:00
|
|
|
KBUILD_BUILTIN :=
|
2017-10-04 03:56:06 +00:00
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# If we have "make <whatever> modules", compile modules
|
|
|
|
|
# in addition to whatever we do anyway.
|
|
|
|
|
# Just "make" or "make all" shall build modules as well
|
|
|
|
|
|
2020-05-11 03:50:13 +00:00
|
|
|
ifneq ($(filter all modules nsdeps,$(MAKECMDGOALS)),)
|
2017-10-04 03:56:06 +00:00
|
|
|
KBUILD_MODULES := 1
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
ifeq ($(MAKECMDGOALS),)
|
|
|
|
|
KBUILD_MODULES := 1
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
export KBUILD_MODULES KBUILD_BUILTIN
|
|
|
|
|
|
2019-08-10 15:53:03 +00:00
|
|
|
ifdef need-config
|
2019-04-27 03:33:36 +00:00
|
|
|
include include/config/auto.conf
|
|
|
|
|
endif
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
|
|
|
|
# Objects we will link into vmlinux / subdirs we need to visit
|
2020-06-01 05:56:57 +00:00
|
|
|
core-y := init/ usr/
|
2019-01-11 09:52:00 +00:00
|
|
|
drivers-y := drivers/ sound/
|
2019-04-27 03:33:36 +00:00
|
|
|
drivers-$(CONFIG_SAMPLES) += samples/
|
2020-06-01 05:56:58 +00:00
|
|
|
drivers-y += net/ virt/
|
2005-04-16 22:20:36 +00:00
|
|
|
libs-y := lib/
|
|
|
|
|
endif # KBUILD_EXTMOD
|
|
|
|
|
|
kbuild: fix endless syncconfig in case arch Makefile sets CROSS_COMPILE
Commit 21c54b774744 ("kconfig: show compiler version text in the top
comment") was intended to detect the compiler upgrade, but Geert
reported a breakage on the m68k build.
The compiler upgrade is detected by the change of the environment
variable, CC_VERSION_TEXT, which contains the first line of the output
from $(CC) --version. Currently, this works well when CROSS_COMPILE
is given via the environment variable or the Make command line.
However, some architectures such as m68k can specify CROSS_COMPILE
from arch/$(SRCARCH)/Makefile as well. In this case, "make ARCH=m68k"
ends up with endless syncconfig loop.
$ make ARCH=m68k defconfig
*** Default configuration is based on 'multi_defconfig'
#
# configuration written to .config
#
$ make ARCH=m68k
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
Things are happening like this:
Because arch/$(SRCARCH)/Makefile is included after CC_VERSION_TEXT
is set, it contains the host compiler version in the defconfig phase.
To create or update auto.conf, the following line is triggered:
include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
$(Q)$(MAKE) -f $(srctree)/Makefile syncconfig
This recurses the top Makefile after arch/$(SRCARCH)/Makefile is
included. CROSS_COMPILE is set to a m68k toolchain prefix and
exported to the recursed Make. Then, syncconfig is invoked with
the target compiler version in CC_VERSION_TEXT.
The Make will restart because auto.conf and auto.conf.cmd have been
updated. At this point, CROSS_COMPILE is reset, so CC_VERSION_TEXT
is set to the host compiler version again. Then, syncconfig is
triggered due to the change of CC_VERSION_TEXT. This loop continues
eternally.
To fix this problem, $(CC_VERSION_TEXT) must be evaluated only after
arch/$(SRCARCH)/Makefile. Setting it earlier is OK as long as it is
defined by using the '=' operator instead of ':='.
For the defconfig phase, $(CC_VERSION_TEXT) is evaluated when Kbuild
descends into scripts/kconfig/, so it contains the target compiler
version correctly.
include/config/auto.conf.cmd references $(CC_VERSION_TEXT) as well,
so it must be included after arch/$(SRCARCH)/Makefile.
Fixes: 21c54b774744 ("kconfig: show compiler version text in the top comment")
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
2018-06-08 00:21:43 +00:00
|
|
|
# The all: target is the default when no target is given on the
|
|
|
|
|
# command line.
|
|
|
|
|
# This allow a user to issue only 'make' to build a kernel including modules
|
|
|
|
|
# Defaults to vmlinux, but the arch makefile usually adds further targets
|
|
|
|
|
all: vmlinux
|
|
|
|
|
|
|
|
|
|
CFLAGS_GCOV := -fprofile-arcs -ftest-coverage \
|
|
|
|
|
$(call cc-option,-fno-tree-loop-im) \
|
|
|
|
|
$(call cc-disable-warning,maybe-uninitialized,)
|
2018-05-28 09:22:04 +00:00
|
|
|
export CFLAGS_GCOV
|
kbuild: fix endless syncconfig in case arch Makefile sets CROSS_COMPILE
Commit 21c54b774744 ("kconfig: show compiler version text in the top
comment") was intended to detect the compiler upgrade, but Geert
reported a breakage on the m68k build.
The compiler upgrade is detected by the change of the environment
variable, CC_VERSION_TEXT, which contains the first line of the output
from $(CC) --version. Currently, this works well when CROSS_COMPILE
is given via the environment variable or the Make command line.
However, some architectures such as m68k can specify CROSS_COMPILE
from arch/$(SRCARCH)/Makefile as well. In this case, "make ARCH=m68k"
ends up with endless syncconfig loop.
$ make ARCH=m68k defconfig
*** Default configuration is based on 'multi_defconfig'
#
# configuration written to .config
#
$ make ARCH=m68k
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
Things are happening like this:
Because arch/$(SRCARCH)/Makefile is included after CC_VERSION_TEXT
is set, it contains the host compiler version in the defconfig phase.
To create or update auto.conf, the following line is triggered:
include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
$(Q)$(MAKE) -f $(srctree)/Makefile syncconfig
This recurses the top Makefile after arch/$(SRCARCH)/Makefile is
included. CROSS_COMPILE is set to a m68k toolchain prefix and
exported to the recursed Make. Then, syncconfig is invoked with
the target compiler version in CC_VERSION_TEXT.
The Make will restart because auto.conf and auto.conf.cmd have been
updated. At this point, CROSS_COMPILE is reset, so CC_VERSION_TEXT
is set to the host compiler version again. Then, syncconfig is
triggered due to the change of CC_VERSION_TEXT. This loop continues
eternally.
To fix this problem, $(CC_VERSION_TEXT) must be evaluated only after
arch/$(SRCARCH)/Makefile. Setting it earlier is OK as long as it is
defined by using the '=' operator instead of ':='.
For the defconfig phase, $(CC_VERSION_TEXT) is evaluated when Kbuild
descends into scripts/kconfig/, so it contains the target compiler
version correctly.
include/config/auto.conf.cmd references $(CC_VERSION_TEXT) as well,
so it must be included after arch/$(SRCARCH)/Makefile.
Fixes: 21c54b774744 ("kconfig: show compiler version text in the top comment")
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
2018-06-08 00:21:43 +00:00
|
|
|
|
tracing/Makefile: Fix handling redefinition of CC_FLAGS_FTRACE
As a Kernel developer, I make heavy use of "make targz-pkg" in order
to locally compile and remotely install my development Kernels. The
nice feature I rely on is that after a normal "make", "make targz-pkg"
only generates the tarball without having to recompile everything.
That was true until commit f28bc3c32c05 ("tracing: Handle
CC_FLAGS_FTRACE more accurately"). After it, running "make targz-pkg"
after "make" will recompile the whole Kernel tree, making my
development workflow much slower.
The Kernel is choosing to recompile everything because it claims the
command line has changed. A diff of the .cmd files show a repeated
-mfentry in one of the files. That is because "make targz-pkg" calls
"make modules_install" and the environment is already populated with
the exported variables, CC_FLAGS_FTRACE being one of them. Then,
-mfentry gets duplicated because it is not protected behind an ifndef
block, like -pg.
To complicate the problem a little bit more, architectures can define
their own version CC_FLAGS_FTRACE, so our code not only has to
consider recursive Makefiles, but also architecture overrides.
So in this patch we move CC_FLAGS_FTRACE up and unconditionally
define it to -pg. Then we let the architecture Makefiles possibly
override it, and finally append the extra options later. This ensures
the variable is always fully redefined at each invocation so recursive
Makefiles don't keep appending, and hopefully it maintains the
intended behavior on how architectures can override the defaults..
Thanks Steven Rostedt and Vasily Gorbik for the help on this
regression.
Cc: Michal Marek <michal.lkml@markovi.net>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: linux-kbuild@vger.kernel.org
Fixes: commit f28bc3c32c05 ("tracing: Handle CC_FLAGS_FTRACE more accurately")
Acked-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
2018-09-10 17:59:56 +00:00
|
|
|
# The arch Makefiles can override CC_FLAGS_FTRACE. We may also append it later.
|
|
|
|
|
ifdef CONFIG_FUNCTION_TRACER
|
|
|
|
|
CC_FLAGS_FTRACE := -pg
|
|
|
|
|
endif
|
|
|
|
|
|
2019-03-26 06:11:12 +00:00
|
|
|
RETPOLINE_CFLAGS_GCC := -mindirect-branch=thunk-extern -mindirect-branch-register
|
|
|
|
|
RETPOLINE_VDSO_CFLAGS_GCC := -mindirect-branch=thunk-inline -mindirect-branch-register
|
|
|
|
|
RETPOLINE_CFLAGS_CLANG := -mretpoline-external-thunk
|
|
|
|
|
RETPOLINE_VDSO_CFLAGS_CLANG := -mretpoline
|
|
|
|
|
RETPOLINE_CFLAGS := $(call cc-option,$(RETPOLINE_CFLAGS_GCC),$(call cc-option,$(RETPOLINE_CFLAGS_CLANG)))
|
|
|
|
|
RETPOLINE_VDSO_CFLAGS := $(call cc-option,$(RETPOLINE_VDSO_CFLAGS_GCC),$(call cc-option,$(RETPOLINE_VDSO_CFLAGS_CLANG)))
|
|
|
|
|
export RETPOLINE_CFLAGS
|
|
|
|
|
export RETPOLINE_VDSO_CFLAGS
|
|
|
|
|
|
kbuild: fix endless syncconfig in case arch Makefile sets CROSS_COMPILE
Commit 21c54b774744 ("kconfig: show compiler version text in the top
comment") was intended to detect the compiler upgrade, but Geert
reported a breakage on the m68k build.
The compiler upgrade is detected by the change of the environment
variable, CC_VERSION_TEXT, which contains the first line of the output
from $(CC) --version. Currently, this works well when CROSS_COMPILE
is given via the environment variable or the Make command line.
However, some architectures such as m68k can specify CROSS_COMPILE
from arch/$(SRCARCH)/Makefile as well. In this case, "make ARCH=m68k"
ends up with endless syncconfig loop.
$ make ARCH=m68k defconfig
*** Default configuration is based on 'multi_defconfig'
#
# configuration written to .config
#
$ make ARCH=m68k
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
Things are happening like this:
Because arch/$(SRCARCH)/Makefile is included after CC_VERSION_TEXT
is set, it contains the host compiler version in the defconfig phase.
To create or update auto.conf, the following line is triggered:
include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
$(Q)$(MAKE) -f $(srctree)/Makefile syncconfig
This recurses the top Makefile after arch/$(SRCARCH)/Makefile is
included. CROSS_COMPILE is set to a m68k toolchain prefix and
exported to the recursed Make. Then, syncconfig is invoked with
the target compiler version in CC_VERSION_TEXT.
The Make will restart because auto.conf and auto.conf.cmd have been
updated. At this point, CROSS_COMPILE is reset, so CC_VERSION_TEXT
is set to the host compiler version again. Then, syncconfig is
triggered due to the change of CC_VERSION_TEXT. This loop continues
eternally.
To fix this problem, $(CC_VERSION_TEXT) must be evaluated only after
arch/$(SRCARCH)/Makefile. Setting it earlier is OK as long as it is
defined by using the '=' operator instead of ':='.
For the defconfig phase, $(CC_VERSION_TEXT) is evaluated when Kbuild
descends into scripts/kconfig/, so it contains the target compiler
version correctly.
include/config/auto.conf.cmd references $(CC_VERSION_TEXT) as well,
so it must be included after arch/$(SRCARCH)/Makefile.
Fixes: 21c54b774744 ("kconfig: show compiler version text in the top comment")
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
2018-06-08 00:21:43 +00:00
|
|
|
include arch/$(SRCARCH)/Makefile
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-08-10 15:53:03 +00:00
|
|
|
ifdef need-config
|
|
|
|
|
ifdef may-sync-config
|
kbuild: fix endless syncconfig in case arch Makefile sets CROSS_COMPILE
Commit 21c54b774744 ("kconfig: show compiler version text in the top
comment") was intended to detect the compiler upgrade, but Geert
reported a breakage on the m68k build.
The compiler upgrade is detected by the change of the environment
variable, CC_VERSION_TEXT, which contains the first line of the output
from $(CC) --version. Currently, this works well when CROSS_COMPILE
is given via the environment variable or the Make command line.
However, some architectures such as m68k can specify CROSS_COMPILE
from arch/$(SRCARCH)/Makefile as well. In this case, "make ARCH=m68k"
ends up with endless syncconfig loop.
$ make ARCH=m68k defconfig
*** Default configuration is based on 'multi_defconfig'
#
# configuration written to .config
#
$ make ARCH=m68k
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
scripts/kconfig/conf --syncconfig Kconfig
Things are happening like this:
Because arch/$(SRCARCH)/Makefile is included after CC_VERSION_TEXT
is set, it contains the host compiler version in the defconfig phase.
To create or update auto.conf, the following line is triggered:
include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
$(Q)$(MAKE) -f $(srctree)/Makefile syncconfig
This recurses the top Makefile after arch/$(SRCARCH)/Makefile is
included. CROSS_COMPILE is set to a m68k toolchain prefix and
exported to the recursed Make. Then, syncconfig is invoked with
the target compiler version in CC_VERSION_TEXT.
The Make will restart because auto.conf and auto.conf.cmd have been
updated. At this point, CROSS_COMPILE is reset, so CC_VERSION_TEXT
is set to the host compiler version again. Then, syncconfig is
triggered due to the change of CC_VERSION_TEXT. This loop continues
eternally.
To fix this problem, $(CC_VERSION_TEXT) must be evaluated only after
arch/$(SRCARCH)/Makefile. Setting it earlier is OK as long as it is
defined by using the '=' operator instead of ':='.
For the defconfig phase, $(CC_VERSION_TEXT) is evaluated when Kbuild
descends into scripts/kconfig/, so it contains the target compiler
version correctly.
include/config/auto.conf.cmd references $(CC_VERSION_TEXT) as well,
so it must be included after arch/$(SRCARCH)/Makefile.
Fixes: 21c54b774744 ("kconfig: show compiler version text in the top comment")
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
2018-06-08 00:21:43 +00:00
|
|
|
# Read in dependencies to all Kconfig* files, make sure to run syncconfig if
|
|
|
|
|
# changes are detected. This should be included after arch/$(SRCARCH)/Makefile
|
|
|
|
|
# because some architectures define CROSS_COMPILE there.
|
kbuild: turn auto.conf.cmd into a mandatory include file
syncconfig is responsible for keeping auto.conf up-to-date, so if it
fails for any reason, the build must be terminated immediately.
However, since commit 9390dff66a52 ("kbuild: invoke syncconfig if
include/config/auto.conf.cmd is missing"), Kbuild continues running
even after syncconfig fails.
You can confirm this by intentionally making syncconfig error out:
diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c
index 08ba146..307b9de 100644
--- a/scripts/kconfig/confdata.c
+++ b/scripts/kconfig/confdata.c
@@ -1023,6 +1023,9 @@ int conf_write_autoconf(int overwrite)
FILE *out, *tristate, *out_h;
int i;
+ if (overwrite)
+ return 1;
+
if (!overwrite && is_present(autoconf_name))
return 0;
Then, syncconfig fails, but Make would not stop:
$ make -s mrproper allyesconfig defconfig
$ make
scripts/kconfig/conf --syncconfig Kconfig
*** Error during sync of the configuration.
make[2]: *** [scripts/kconfig/Makefile;69: syncconfig] Error 1
make[1]: *** [Makefile;557: syncconfig] Error 2
make: *** [include/config/auto.conf.cmd] Deleting file 'include/config/tristate.conf'
make: Failed to remake makefile 'include/config/auto.conf'.
SYSTBL arch/x86/include/generated/asm/syscalls_32.h
SYSHDR arch/x86/include/generated/asm/unistd_32_ia32.h
SYSHDR arch/x86/include/generated/asm/unistd_64_x32.h
SYSTBL arch/x86/include/generated/asm/syscalls_64.h
[ continue running ... ]
The reason is in the behavior of a pattern rule with multi-targets.
%/auto.conf %/auto.conf.cmd %/tristate.conf: $(KCONFIG_CONFIG)
$(Q)$(MAKE) -f $(srctree)/Makefile syncconfig
GNU Make knows this rule is responsible for making all the three files
simultaneously. As far as examined, auto.conf.cmd is the target in
question when this rule is invoked. It is probably because auto.conf.cmd
is included below the inclusion of auto.conf.
The inclusion of auto.conf is mandatory, while that of auto.conf.cmd
is optional. GNU Make does not care about the failure in the process
of updating optional include files.
I filed this issue (https://savannah.gnu.org/bugs/?56301) in case this
behavior could be improved somehow in future releases of GNU Make.
Anyway, it is quite easy to fix our Makefile.
Given that auto.conf is already a mandatory include file, there is no
reason to stick auto.conf.cmd optional. Make it mandatory as well.
Cc: linux-stable <stable@vger.kernel.org> # 5.0+
Fixes: 9390dff66a52 ("kbuild: invoke syncconfig if include/config/auto.conf.cmd is missing")
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-05-12 02:13:48 +00:00
|
|
|
include include/config/auto.conf.cmd
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-02-22 07:40:11 +00:00
|
|
|
$(KCONFIG_CONFIG):
|
|
|
|
|
@echo >&2 '***'
|
|
|
|
|
@echo >&2 '*** Configuration file "$@" not found!'
|
|
|
|
|
@echo >&2 '***'
|
|
|
|
|
@echo >&2 '*** Please run some configurator (e.g. "make oldconfig" or'
|
|
|
|
|
@echo >&2 '*** "make menuconfig" or "make xconfig").'
|
|
|
|
|
@echo >&2 '***'
|
|
|
|
|
@/bin/false
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-02-13 07:58:20 +00:00
|
|
|
# The actual configuration files used during the build are stored in
|
|
|
|
|
# include/generated/ and include/config/. Update them if .config is newer than
|
|
|
|
|
# include/config/auto.conf (which mirrors .config).
|
2019-02-22 07:40:10 +00:00
|
|
|
#
|
|
|
|
|
# This exploits the 'multi-target pattern rule' trick.
|
|
|
|
|
# The syncconfig should be executed only once to make all the targets.
|
2020-03-25 03:16:30 +00:00
|
|
|
# (Note: use the grouped target '&:' when we bump to GNU Make 4.3)
|
2020-05-01 06:01:41 +00:00
|
|
|
%/config/auto.conf %/config/auto.conf.cmd %/generated/autoconf.h: $(KCONFIG_CONFIG)
|
2018-03-01 06:34:37 +00:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/Makefile syncconfig
|
2019-08-10 15:53:03 +00:00
|
|
|
else # !may-sync-config
|
kbuild: do not update config when running install targets
"make syncconfig" is automatically invoked when any of the following
happens:
- .config is updated
- any of Kconfig files is updated
- any of environment variables referenced in Kconfig is changed
Then, it updates configuration files such as include/config/auto.conf
include/generated/autoconf.h, etc.
Even install targets (install, modules_install, etc.) are no exception.
However, they should never ever modify the source tree. Install
targets are often run with root privileges. Once those configuration
files are owned by root, "make mrproper" would end up with permission
error.
Install targets should just copy things blindly. They should not care
whether the configuration is up-to-date or not. This makes more sense
because we are interested in the configuration that was used in the
previous kernel building.
This issue has existed since before, but rarely happened. I expect
more chance where people are hit by this; with the new Kconfig syntax
extension, the .config now contains the compiler information. If you
cross-compile the kernel with CROSS_COMPILE, but forget to pass it
for "make install", you meet "any of environment variables referenced
in Kconfig is changed" because $(CC) is referenced in Kconfig.
Another scenario is the compiler upgrade before the installation.
Install targets need the configuration. "make modules_install" refer
to CONFIG_MODULES etc. "make dtbs_install" also needs CONFIG_ARCH_*
to decide which dtb files to install. However, the auto-update of
the configuration files should be avoided. We already do this for
external modules.
Now, Make targets are categorized into 3 groups:
[1] Do not need the kernel configuration at all
help, coccicheck, headers_install etc.
[2] Need the latest kernel configuration
If new config options are added, Kconfig will show prompt to
ask user's selection.
Build targets such as vmlinux, in-kernel modules are the cases.
[3] Need the kernel configuration, but do not want to update it
Install targets except headers_install, and external modules
are the cases.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2018-07-20 07:46:34 +00:00
|
|
|
# External modules and some install targets need include/generated/autoconf.h
|
|
|
|
|
# and include/config/auto.conf but do not care if they are up-to-date.
|
|
|
|
|
# Use auto.conf to trigger the test
|
2006-08-07 19:01:36 +00:00
|
|
|
PHONY += include/config/auto.conf
|
|
|
|
|
|
|
|
|
|
include/config/auto.conf:
|
2009-10-17 22:49:24 +00:00
|
|
|
$(Q)test -e include/generated/autoconf.h -a -e $@ || ( \
|
2012-07-07 21:04:40 +00:00
|
|
|
echo >&2; \
|
|
|
|
|
echo >&2 " ERROR: Kernel configuration is invalid."; \
|
|
|
|
|
echo >&2 " include/generated/autoconf.h or $@ are missing.";\
|
|
|
|
|
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
|
|
|
|
|
echo >&2 ; \
|
2006-08-07 19:01:36 +00:00
|
|
|
/bin/false)
|
|
|
|
|
|
kbuild: do not update config when running install targets
"make syncconfig" is automatically invoked when any of the following
happens:
- .config is updated
- any of Kconfig files is updated
- any of environment variables referenced in Kconfig is changed
Then, it updates configuration files such as include/config/auto.conf
include/generated/autoconf.h, etc.
Even install targets (install, modules_install, etc.) are no exception.
However, they should never ever modify the source tree. Install
targets are often run with root privileges. Once those configuration
files are owned by root, "make mrproper" would end up with permission
error.
Install targets should just copy things blindly. They should not care
whether the configuration is up-to-date or not. This makes more sense
because we are interested in the configuration that was used in the
previous kernel building.
This issue has existed since before, but rarely happened. I expect
more chance where people are hit by this; with the new Kconfig syntax
extension, the .config now contains the compiler information. If you
cross-compile the kernel with CROSS_COMPILE, but forget to pass it
for "make install", you meet "any of environment variables referenced
in Kconfig is changed" because $(CC) is referenced in Kconfig.
Another scenario is the compiler upgrade before the installation.
Install targets need the configuration. "make modules_install" refer
to CONFIG_MODULES etc. "make dtbs_install" also needs CONFIG_ARCH_*
to decide which dtb files to install. However, the auto-update of
the configuration files should be avoided. We already do this for
external modules.
Now, Make targets are categorized into 3 groups:
[1] Do not need the kernel configuration at all
help, coccicheck, headers_install etc.
[2] Need the latest kernel configuration
If new config options are added, Kconfig will show prompt to
ask user's selection.
Build targets such as vmlinux, in-kernel modules are the cases.
[3] Need the kernel configuration, but do not want to update it
Install targets except headers_install, and external modules
are the cases.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2018-07-20 07:46:34 +00:00
|
|
|
endif # may-sync-config
|
2019-08-10 15:53:03 +00:00
|
|
|
endif # need-config
|
2005-04-16 22:20:36 +00:00
|
|
|
|
Makefile: Fix unrecognized cross-compiler command line options
On architectures that setup CROSS_COMPILE in their arch/*/Makefile
(arc, blackfin, m68k, mips, parisc, score, sh, tile, unicore32, xtensa),
cc-option and cc-disable-warning may check against the wrong compiler,
causing errors like
cc1: error: unrecognized command line option "-Wno-maybe-uninitialized"
if the host gcc supports a compiler option, while the cross compiler
doesn't support that option.
Move all logic using cc-option or cc-disable-warning below the inclusion
of the arch's Makefile to fix this.
Introduced by
- commit e74fc973b6e531fef1fce8b101ffff05ecfb774c ("Turn off
-Wmaybe-uninitialized when building with -Os"),
- commit 61163efae02040f66a95c8ed17f4407951ba58fa ("kbuild: LLVMLinux:
Add Kbuild support for building kernel with Clang").
As -Wno-maybe-uninitialized requires a quite recent gcc (gcc 4.6.3 on
Ubuntu 12.04 LTS doesn't support it), this only showed up recently (gcc
4.8.2 on Ubuntu 14.04 LTS does support it).
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Michal Marek <mmarek@suse.cz>
2014-05-27 07:54:12 +00:00
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fno-delete-null-pointer-checks,)
|
2016-10-12 17:23:41 +00:00
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning,frame-address,)
|
2017-07-13 02:25:47 +00:00
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, format-truncation)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, format-overflow)
|
2019-05-01 18:05:41 +00:00
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, address-of-packed-member)
|
Makefile: Fix unrecognized cross-compiler command line options
On architectures that setup CROSS_COMPILE in their arch/*/Makefile
(arc, blackfin, m68k, mips, parisc, score, sh, tile, unicore32, xtensa),
cc-option and cc-disable-warning may check against the wrong compiler,
causing errors like
cc1: error: unrecognized command line option "-Wno-maybe-uninitialized"
if the host gcc supports a compiler option, while the cross compiler
doesn't support that option.
Move all logic using cc-option or cc-disable-warning below the inclusion
of the arch's Makefile to fix this.
Introduced by
- commit e74fc973b6e531fef1fce8b101ffff05ecfb774c ("Turn off
-Wmaybe-uninitialized when building with -Os"),
- commit 61163efae02040f66a95c8ed17f4407951ba58fa ("kbuild: LLVMLinux:
Add Kbuild support for building kernel with Clang").
As -Wno-maybe-uninitialized requires a quite recent gcc (gcc 4.6.3 on
Ubuntu 12.04 LTS doesn't support it), this only showed up recently (gcc
4.8.2 on Ubuntu 14.04 LTS does support it).
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Michal Marek <mmarek@suse.cz>
2014-05-27 07:54:12 +00:00
|
|
|
|
2019-08-20 17:09:40 +00:00
|
|
|
ifdef CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE
|
|
|
|
|
KBUILD_CFLAGS += -O2
|
|
|
|
|
else ifdef CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE_O3
|
|
|
|
|
KBUILD_CFLAGS += -O3
|
|
|
|
|
else ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
|
|
|
|
|
KBUILD_CFLAGS += -Os
|
2016-04-25 15:35:28 +00:00
|
|
|
endif
|
2005-04-16 22:20:36 +00:00
|
|
|
|
./Makefile: tell gcc optimizer to never introduce new data races
We have been chasing a memory corruption bug, which turned out to be
caused by very old gcc (4.3.4), which happily turned conditional load
into a non-conditional one, and that broke correctness (the condition
was met only if lock was held) and corrupted memory.
This particular problem with that particular code did not happen when
never gccs were used. I've brought this up with our gcc folks, as I
wanted to make sure that this can't really happen again, and it turns
out it actually can.
Quoting Martin Jambor <mjambor@suse.cz>:
"More current GCCs are more careful when it comes to replacing a
conditional load with a non-conditional one, most notably they check
that a store happens in each iteration of _a_ loop but they assume
loops are executed. They also perform a simple check whether the
store cannot trap which currently passes only for non-const
variables. A simple testcase demonstrating it on an x86_64 is for
example the following:
$ cat cond_store.c
int g_1 = 1;
int g_2[1024] __attribute__((section ("safe_section"), aligned (4096)));
int c = 4;
int __attribute__ ((noinline))
foo (void)
{
int l;
for (l = 0; (l != 4); l++) {
if (g_1)
return l;
for (g_2[0] = 0; (g_2[0] >= 26); ++g_2[0])
;
}
return 2;
}
int main (int argc, char* argv[])
{
if (mprotect (g_2, sizeof(g_2), PROT_READ) == -1)
{
int e = errno;
error (e, e, "mprotect error %i", e);
}
foo ();
__builtin_printf("OK\n");
return 0;
}
/* EOF */
$ ~/gcc/trunk/inst/bin/gcc cond_store.c -O2 --param allow-store-data-races=0
$ ./a.out
OK
$ ~/gcc/trunk/inst/bin/gcc cond_store.c -O2 --param allow-store-data-races=1
$ ./a.out
Segmentation fault
The testcase fails the same at least with 4.9, 4.8 and 4.7. Therefore
I would suggest building kernels with this parameter set to zero. I
also agree with Jikos that the default should be changed for -O2. I
have run most of the SPEC 2k6 CPU benchmarks (gamess and dealII
failed, at -O2, not sure why) compiled with and without this option
and did not see any real difference between respective run-times"
Hopefully the default will be changed in newer gccs, but let's force it
for kernel builds so that we are on a safe side even when older gcc are
used.
The code in question was out-of-tree printk-in-NMI (yeah, surprise
suprise, once again) patch written by Petr Mladek, let me quote his
comment from our internal bugzilla:
"I have spent few days investigating inconsistent state of kernel ring buffer.
It went out that it was caused by speculative store generated by
gcc-4.3.4.
The problem is in assembly generated for make_free_space(). The functions is
called the following way:
+ vprintk_emit();
+ log = MAIN_LOG; // with logbuf_lock
or
log = NMI_LOG; // with nmi_logbuf_lock
cont_add(log, ...);
+ cont_flush(log, ...);
+ log_store(log, ...);
+ log_make_free_space(log, ...);
If called with log = NMI_LOG then only nmi_log_* global variables are safe to
modify but the generated code does store also into (main_)log_* global
variables:
<log_make_free_space>:
55 push %rbp
89 f6 mov %esi,%esi
48 8b 05 03 99 51 01 mov 0x1519903(%rip),%rax # ffffffff82620868 <nmi_log_next_id>
44 8b 1d ec 98 51 01 mov 0x15198ec(%rip),%r11d # ffffffff82620858 <log_next_idx>
8b 35 36 60 14 01 mov 0x1146036(%rip),%esi # ffffffff8224cfa8 <log_buf_len>
44 8b 35 33 60 14 01 mov 0x1146033(%rip),%r14d # ffffffff8224cfac <nmi_log_buf_len>
4c 8b 2d d0 98 51 01 mov 0x15198d0(%rip),%r13 # ffffffff82620850 <log_next_seq>
4c 8b 25 11 61 14 01 mov 0x1146111(%rip),%r12 # ffffffff8224d098 <log_buf>
49 89 c2 mov %rax,%r10
48 21 c2 and %rax,%rdx
48 8b 1d 0c 99 55 01 mov 0x155990c(%rip),%rbx # ffffffff826608a0 <nmi_log_buf>
49 c1 ea 20 shr $0x20,%r10
48 89 55 d0 mov %rdx,-0x30(%rbp)
44 29 de sub %r11d,%esi
45 29 d6 sub %r10d,%r14d
4c 8b 0d 97 98 51 01 mov 0x1519897(%rip),%r9 # ffffffff82620840 <log_first_seq>
eb 7e jmp ffffffff81107029 <log_make_free_space+0xe9>
[...]
85 ff test %edi,%edi # edi = 1 for NMI_LOG
4c 89 e8 mov %r13,%rax
4c 89 ca mov %r9,%rdx
74 0a je ffffffff8110703d <log_make_free_space+0xfd>
8b 15 27 98 51 01 mov 0x1519827(%rip),%edx # ffffffff82620860 <nmi_log_first_id>
48 8b 45 d0 mov -0x30(%rbp),%rax
48 39 c2 cmp %rax,%rdx # end of loop
0f 84 da 00 00 00 je ffffffff81107120 <log_make_free_space+0x1e0>
[...]
85 ff test %edi,%edi # edi = 1 for NMI_LOG
4c 89 0d 17 97 51 01 mov %r9,0x1519717(%rip) # ffffffff82620840 <log_first_seq>
^^^^^^^^^^^^^^^^^^^^^^^^^^
KABOOOM
74 35 je ffffffff81107160 <log_make_free_space+0x220>
It stores log_first_seq when edi == NMI_LOG. This instructions are used also
when edi == MAIN_LOG but the store is done speculatively before the condition
is decided. It is unsafe because we do not have "logbuf_lock" in NMI context
and some other process migh modify "log_first_seq" in parallel"
I believe that the best course of action is both
- building kernel (and anything multi-threaded, I guess) with that
optimization turned off
- persuade gcc folks to change the default for future releases
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Cc: Martin Jambor <mjambor@suse.cz>
Cc: Petr Mladek <pmladek@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Marek Polacek <polacek@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>
Cc: Steven Noonan <steven@uplinklabs.net>
Cc: Richard Biener <richard.guenther@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-08-06 23:08:43 +00:00
|
|
|
# Tell gcc to never replace conditional load with a non-conditional one
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,--param=allow-store-data-races=0)
|
2020-03-17 00:07:18 +00:00
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fno-allow-store-data-races)
|
./Makefile: tell gcc optimizer to never introduce new data races
We have been chasing a memory corruption bug, which turned out to be
caused by very old gcc (4.3.4), which happily turned conditional load
into a non-conditional one, and that broke correctness (the condition
was met only if lock was held) and corrupted memory.
This particular problem with that particular code did not happen when
never gccs were used. I've brought this up with our gcc folks, as I
wanted to make sure that this can't really happen again, and it turns
out it actually can.
Quoting Martin Jambor <mjambor@suse.cz>:
"More current GCCs are more careful when it comes to replacing a
conditional load with a non-conditional one, most notably they check
that a store happens in each iteration of _a_ loop but they assume
loops are executed. They also perform a simple check whether the
store cannot trap which currently passes only for non-const
variables. A simple testcase demonstrating it on an x86_64 is for
example the following:
$ cat cond_store.c
int g_1 = 1;
int g_2[1024] __attribute__((section ("safe_section"), aligned (4096)));
int c = 4;
int __attribute__ ((noinline))
foo (void)
{
int l;
for (l = 0; (l != 4); l++) {
if (g_1)
return l;
for (g_2[0] = 0; (g_2[0] >= 26); ++g_2[0])
;
}
return 2;
}
int main (int argc, char* argv[])
{
if (mprotect (g_2, sizeof(g_2), PROT_READ) == -1)
{
int e = errno;
error (e, e, "mprotect error %i", e);
}
foo ();
__builtin_printf("OK\n");
return 0;
}
/* EOF */
$ ~/gcc/trunk/inst/bin/gcc cond_store.c -O2 --param allow-store-data-races=0
$ ./a.out
OK
$ ~/gcc/trunk/inst/bin/gcc cond_store.c -O2 --param allow-store-data-races=1
$ ./a.out
Segmentation fault
The testcase fails the same at least with 4.9, 4.8 and 4.7. Therefore
I would suggest building kernels with this parameter set to zero. I
also agree with Jikos that the default should be changed for -O2. I
have run most of the SPEC 2k6 CPU benchmarks (gamess and dealII
failed, at -O2, not sure why) compiled with and without this option
and did not see any real difference between respective run-times"
Hopefully the default will be changed in newer gccs, but let's force it
for kernel builds so that we are on a safe side even when older gcc are
used.
The code in question was out-of-tree printk-in-NMI (yeah, surprise
suprise, once again) patch written by Petr Mladek, let me quote his
comment from our internal bugzilla:
"I have spent few days investigating inconsistent state of kernel ring buffer.
It went out that it was caused by speculative store generated by
gcc-4.3.4.
The problem is in assembly generated for make_free_space(). The functions is
called the following way:
+ vprintk_emit();
+ log = MAIN_LOG; // with logbuf_lock
or
log = NMI_LOG; // with nmi_logbuf_lock
cont_add(log, ...);
+ cont_flush(log, ...);
+ log_store(log, ...);
+ log_make_free_space(log, ...);
If called with log = NMI_LOG then only nmi_log_* global variables are safe to
modify but the generated code does store also into (main_)log_* global
variables:
<log_make_free_space>:
55 push %rbp
89 f6 mov %esi,%esi
48 8b 05 03 99 51 01 mov 0x1519903(%rip),%rax # ffffffff82620868 <nmi_log_next_id>
44 8b 1d ec 98 51 01 mov 0x15198ec(%rip),%r11d # ffffffff82620858 <log_next_idx>
8b 35 36 60 14 01 mov 0x1146036(%rip),%esi # ffffffff8224cfa8 <log_buf_len>
44 8b 35 33 60 14 01 mov 0x1146033(%rip),%r14d # ffffffff8224cfac <nmi_log_buf_len>
4c 8b 2d d0 98 51 01 mov 0x15198d0(%rip),%r13 # ffffffff82620850 <log_next_seq>
4c 8b 25 11 61 14 01 mov 0x1146111(%rip),%r12 # ffffffff8224d098 <log_buf>
49 89 c2 mov %rax,%r10
48 21 c2 and %rax,%rdx
48 8b 1d 0c 99 55 01 mov 0x155990c(%rip),%rbx # ffffffff826608a0 <nmi_log_buf>
49 c1 ea 20 shr $0x20,%r10
48 89 55 d0 mov %rdx,-0x30(%rbp)
44 29 de sub %r11d,%esi
45 29 d6 sub %r10d,%r14d
4c 8b 0d 97 98 51 01 mov 0x1519897(%rip),%r9 # ffffffff82620840 <log_first_seq>
eb 7e jmp ffffffff81107029 <log_make_free_space+0xe9>
[...]
85 ff test %edi,%edi # edi = 1 for NMI_LOG
4c 89 e8 mov %r13,%rax
4c 89 ca mov %r9,%rdx
74 0a je ffffffff8110703d <log_make_free_space+0xfd>
8b 15 27 98 51 01 mov 0x1519827(%rip),%edx # ffffffff82620860 <nmi_log_first_id>
48 8b 45 d0 mov -0x30(%rbp),%rax
48 39 c2 cmp %rax,%rdx # end of loop
0f 84 da 00 00 00 je ffffffff81107120 <log_make_free_space+0x1e0>
[...]
85 ff test %edi,%edi # edi = 1 for NMI_LOG
4c 89 0d 17 97 51 01 mov %r9,0x1519717(%rip) # ffffffff82620840 <log_first_seq>
^^^^^^^^^^^^^^^^^^^^^^^^^^
KABOOOM
74 35 je ffffffff81107160 <log_make_free_space+0x220>
It stores log_first_seq when edi == NMI_LOG. This instructions are used also
when edi == MAIN_LOG but the store is done speculatively before the condition
is decided. It is unsafe because we do not have "logbuf_lock" in NMI context
and some other process migh modify "log_first_seq" in parallel"
I believe that the best course of action is both
- building kernel (and anything multi-threaded, I guess) with that
optimization turned off
- persuade gcc folks to change the default for future releases
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Cc: Martin Jambor <mjambor@suse.cz>
Cc: Petr Mladek <pmladek@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Marek Polacek <polacek@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>
Cc: Steven Noonan <steven@uplinklabs.net>
Cc: Richard Biener <richard.guenther@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-08-06 23:08:43 +00:00
|
|
|
|
2017-11-17 23:30:50 +00:00
|
|
|
include scripts/Makefile.kcov
|
2016-05-23 22:09:38 +00:00
|
|
|
include scripts/Makefile.gcc-plugins
|
|
|
|
|
|
2012-03-28 18:51:18 +00:00
|
|
|
ifdef CONFIG_READABLE_ASM
|
|
|
|
|
# Disable optimizations that make assembler listings hard to read.
|
|
|
|
|
# reorder blocks reorders the control in the function
|
|
|
|
|
# ipa clone creates specialized cloned functions
|
|
|
|
|
# partial inlining inlines only parts of functions
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fno-reorder-blocks,) \
|
|
|
|
|
$(call cc-option,-fno-ipa-cp-clone,) \
|
|
|
|
|
$(call cc-option,-fno-partial-inlining)
|
|
|
|
|
endif
|
|
|
|
|
|
2009-06-04 23:29:08 +00:00
|
|
|
ifneq ($(CONFIG_FRAME_WARN),0)
|
2020-02-16 15:19:36 +00:00
|
|
|
KBUILD_CFLAGS += -Wframe-larger-than=$(CONFIG_FRAME_WARN)
|
2008-02-22 14:15:03 +00:00
|
|
|
endif
|
|
|
|
|
|
stack-protector: test compiler capability in Kconfig and drop AUTO mode
Move the test for -fstack-protector(-strong) option to Kconfig.
If the compiler does not support the option, the corresponding menu
is automatically hidden. If STRONG is not supported, it will fall
back to REGULAR. If REGULAR is not supported, it will be disabled.
This means, AUTO is implicitly handled by the dependency solver of
Kconfig, hence removed.
I also turned the 'choice' into only two boolean symbols. The use of
'choice' is not a good idea here, because all of all{yes,mod,no}config
would choose the first visible value, while we want allnoconfig to
disable as many features as possible.
X86 has additional shell scripts in case the compiler supports those
options, but generates broken code. I added CC_HAS_SANE_STACKPROTECTOR
to test this. I had to add -m32 to gcc-x86_32-has-stack-protector.sh
to make it work correctly.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Kees Cook <keescook@chromium.org>
2018-05-28 09:22:00 +00:00
|
|
|
stackp-flags-$(CONFIG_CC_HAS_STACKPROTECTOR_NONE) := -fno-stack-protector
|
Kbuild: rename CC_STACKPROTECTOR[_STRONG] config variables
The changes to automatically test for working stack protector compiler
support in the Kconfig files removed the special STACKPROTECTOR_AUTO
option that picked the strongest stack protector that the compiler
supported.
That was all a nice cleanup - it makes no sense to have the AUTO case
now that the Kconfig phase can just determine the compiler support
directly.
HOWEVER.
It also meant that doing "make oldconfig" would now _disable_ the strong
stackprotector if you had AUTO enabled, because in a legacy config file,
the sane stack protector configuration would look like
CONFIG_HAVE_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_NONE is not set
# CONFIG_CC_STACKPROTECTOR_REGULAR is not set
# CONFIG_CC_STACKPROTECTOR_STRONG is not set
CONFIG_CC_STACKPROTECTOR_AUTO=y
and when you ran this through "make oldconfig" with the Kbuild changes,
it would ask you about the regular CONFIG_CC_STACKPROTECTOR (that had
been renamed from CONFIG_CC_STACKPROTECTOR_REGULAR to just
CONFIG_CC_STACKPROTECTOR), but it would think that the STRONG version
used to be disabled (because it was really enabled by AUTO), and would
disable it in the new config, resulting in:
CONFIG_HAVE_CC_STACKPROTECTOR=y
CONFIG_CC_HAS_STACKPROTECTOR_NONE=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_STRONG is not set
CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
That's dangerously subtle - people could suddenly find themselves with
the weaker stack protector setup without even realizing.
The solution here is to just rename not just the old RECULAR stack
protector option, but also the strong one. This does that by just
removing the CC_ prefix entirely for the user choices, because it really
is not about the compiler support (the compiler support now instead
automatially impacts _visibility_ of the options to users).
This results in "make oldconfig" actually asking the user for their
choice, so that we don't have any silent subtle security model changes.
The end result would generally look like this:
CONFIG_HAVE_CC_STACKPROTECTOR=y
CONFIG_CC_HAS_STACKPROTECTOR_NONE=y
CONFIG_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR_STRONG=y
CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
where the "CC_" versions really are about internal compiler
infrastructure, not the user selections.
Acked-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-06-14 03:21:18 +00:00
|
|
|
stackp-flags-$(CONFIG_STACKPROTECTOR) := -fstack-protector
|
|
|
|
|
stackp-flags-$(CONFIG_STACKPROTECTOR_STRONG) := -fstack-protector-strong
|
stack-protector: test compiler capability in Kconfig and drop AUTO mode
Move the test for -fstack-protector(-strong) option to Kconfig.
If the compiler does not support the option, the corresponding menu
is automatically hidden. If STRONG is not supported, it will fall
back to REGULAR. If REGULAR is not supported, it will be disabled.
This means, AUTO is implicitly handled by the dependency solver of
Kconfig, hence removed.
I also turned the 'choice' into only two boolean symbols. The use of
'choice' is not a good idea here, because all of all{yes,mod,no}config
would choose the first visible value, while we want allnoconfig to
disable as many features as possible.
X86 has additional shell scripts in case the compiler supports those
options, but generates broken code. I added CC_HAS_SANE_STACKPROTECTOR
to test this. I had to add -m32 to gcc-x86_32-has-stack-protector.sh
to make it work correctly.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Kees Cook <keescook@chromium.org>
2018-05-28 09:22:00 +00:00
|
|
|
|
|
|
|
|
KBUILD_CFLAGS += $(stackp-flags-y)
|
2008-02-13 21:43:28 +00:00
|
|
|
|
2018-10-30 13:26:33 +00:00
|
|
|
ifdef CONFIG_CC_IS_CLANG
|
2019-05-10 14:10:09 +00:00
|
|
|
KBUILD_CPPFLAGS += -Qunused-arguments
|
|
|
|
|
KBUILD_CFLAGS += -Wno-format-invalid-specifier
|
|
|
|
|
KBUILD_CFLAGS += -Wno-gnu
|
2017-11-27 12:15:13 +00:00
|
|
|
# CLANG uses a _MergedGlobals as optimization, but this breaks modpost, as the
|
|
|
|
|
# source of a reference will be _MergedGlobals and not on of the whitelisted names.
|
|
|
|
|
# See modpost pattern 2
|
2019-05-10 14:10:09 +00:00
|
|
|
KBUILD_CFLAGS += -mno-global-merge
|
2017-11-27 12:15:13 +00:00
|
|
|
else
|
|
|
|
|
|
|
|
|
|
# These warnings generated too much noise in a regular build.
|
|
|
|
|
# Use make W=1 to enable them (see scripts/Makefile.extrawarn)
|
2018-10-02 01:32:23 +00:00
|
|
|
KBUILD_CFLAGS += -Wno-unused-but-set-variable
|
2019-08-27 00:41:55 +00:00
|
|
|
|
|
|
|
|
# Warn about unmarked fall-throughs in switch statement.
|
|
|
|
|
# Disabled for clang while comment to attribute conversion happens and
|
|
|
|
|
# https://github.com/ClangBuiltLinux/linux/issues/636 is discussed.
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Wimplicit-fallthrough,)
|
2017-11-27 12:15:13 +00:00
|
|
|
endif
|
|
|
|
|
|
2018-02-06 23:46:51 +00:00
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, unused-const-variable)
|
2005-04-16 22:20:36 +00:00
|
|
|
ifdef CONFIG_FRAME_POINTER
|
2007-10-14 20:21:35 +00:00
|
|
|
KBUILD_CFLAGS += -fno-omit-frame-pointer -fno-optimize-sibling-calls
|
2005-04-16 22:20:36 +00:00
|
|
|
else
|
2010-08-10 18:20:53 +00:00
|
|
|
# Some targets (ARM with Thumb2, for example), can't be built with frame
|
|
|
|
|
# pointers. For those, we don't have FUNCTION_TRACER automatically
|
|
|
|
|
# select FRAME_POINTER. However, FUNCTION_TRACER adds -pg, and this is
|
|
|
|
|
# incompatible with -fomit-frame-pointer with current GCC, so we don't use
|
|
|
|
|
# -fomit-frame-pointer with FUNCTION_TRACER.
|
|
|
|
|
ifndef CONFIG_FUNCTION_TRACER
|
2007-10-14 20:21:35 +00:00
|
|
|
KBUILD_CFLAGS += -fomit-frame-pointer
|
2005-04-16 22:20:36 +00:00
|
|
|
endif
|
2010-08-10 18:20:53 +00:00
|
|
|
endif
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-04-10 15:48:31 +00:00
|
|
|
# Initialize all stack variables with a pattern, if desired.
|
|
|
|
|
ifdef CONFIG_INIT_STACK_ALL
|
|
|
|
|
KBUILD_CFLAGS += -ftrivial-auto-var-init=pattern
|
|
|
|
|
endif
|
|
|
|
|
|
kbuild: Disable extra debugging info in .s output
Modern gcc adds view assignments, reset assertion checking in .loc
directives and a couple more additional debug markers, which clutters
the asm output unnecessarily:
For example:
bsp_resume:
.LFB3466:
.loc 1 1868 1 is_stmt 1 view -0
.cfi_startproc
.loc 1 1869 2 view .LVU73
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
.loc 1 1869 14 is_stmt 0 view .LVU74
movq this_cpu(%rip), %rax # this_cpu, this_cpu
movq 64(%rax), %rax # this_cpu.94_1->c_bsp_resume, _2
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
.loc 1 1869 5 view .LVU75
testq %rax, %rax # _2
je .L8 #,
.loc 1 1870 3 is_stmt 1 view .LVU76
movq $boot_cpu_data, %rdi #,
jmp __x86_indirect_thunk_rax
or
.loc 2 57 9 view .LVU478
.loc 2 57 9 view .LVU479
.loc 2 57 9 view .LVU480
.loc 2 57 9 view .LVU481
.LBB1385:
.LBB1383:
.LBB1379:
.LBB1377:
.LBB1375:
.loc 2 57 9 view .LVU482
.loc 2 57 9 view .LVU483
movl %edi, %edx # cpu, cpu
.LVL87:
.loc 2 57 9 is_stmt 0 view .LVU484
That MOV in there is drowned in debugging information and latter makes
it hard to follow the asm. And that DWARF info is not really needed for
asm output staring.
Disable the debug information generation which clutters the asm output
unnecessarily:
bsp_resume:
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
movq this_cpu(%rip), %rax # this_cpu, this_cpu
movq 64(%rax), %rax # this_cpu.94_1->c_bsp_resume, _2
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
testq %rax, %rax # _2
je .L8 #,
# arch/x86/kernel/cpu/common.c:1870: this_cpu->c_bsp_resume(&boot_cpu_data);
movq $boot_cpu_data, %rdi #,
jmp __x86_indirect_thunk_rax
.L8:
# arch/x86/kernel/cpu/common.c:1871: }
rep ret
.size bsp_resume, .-bsp_resume
[ bp: write commit message. ]
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
2019-02-10 06:51:00 +00:00
|
|
|
DEBUG_CFLAGS := $(call cc-option, -fno-var-tracking-assignments)
|
Fix gcc-4.9.0 miscompilation of load_balance() in scheduler
Michel Dänzer and a couple of other people reported inexplicable random
oopses in the scheduler, and the cause turns out to be gcc mis-compiling
the load_balance() function when debugging is enabled. The gcc bug
apparently goes back to gcc-4.5, but slight optimization changes means
that it now showed up as a problem in 4.9.0 and 4.9.1.
The instruction scheduling problem causes gcc to schedule a spill
operation to before the stack frame has been created, which in turn can
corrupt the spilled value if an interrupt comes in. There may be other
effects of this bug too, but that's the code generation problem seen in
Michel's case.
This is fixed in current gcc HEAD, but the workaround as suggested by
Markus Trippelsdorf is pretty simple: use -fno-var-tracking-assignments
when compiling the kernel, which disables the gcc code that causes the
problem. This can result in slightly worse debug information for
variable accesses, but that is infinitely preferable to actual code
generation problems.
Doing this unconditionally (not just for CONFIG_DEBUG_INFO) also allows
non-debug builds to verify that the debug build would be identical: we
can do
export GCC_COMPARE_DEBUG=1
to make gcc internally verify that the result of the build is
independent of the "-g" flag (it will make the compiler build everything
twice, toggling the debug flag, and compare the results).
Without the "-fno-var-tracking-assignments" option, the build would fail
(even with 4.8.3 that didn't show the actual stack frame bug) with a gcc
compare failure.
See also gcc bugzilla:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61801
Reported-by: Michel Dänzer <michel@daenzer.net>
Suggested-by: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Jakub Jelinek <jakub@redhat.com>
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-07-26 21:52:01 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
ifdef CONFIG_DEBUG_INFO
|
2014-07-30 18:50:18 +00:00
|
|
|
ifdef CONFIG_DEBUG_INFO_SPLIT
|
2019-02-22 07:56:09 +00:00
|
|
|
DEBUG_CFLAGS += -gsplit-dwarf
|
2014-07-30 18:50:18 +00:00
|
|
|
else
|
kbuild: Disable extra debugging info in .s output
Modern gcc adds view assignments, reset assertion checking in .loc
directives and a couple more additional debug markers, which clutters
the asm output unnecessarily:
For example:
bsp_resume:
.LFB3466:
.loc 1 1868 1 is_stmt 1 view -0
.cfi_startproc
.loc 1 1869 2 view .LVU73
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
.loc 1 1869 14 is_stmt 0 view .LVU74
movq this_cpu(%rip), %rax # this_cpu, this_cpu
movq 64(%rax), %rax # this_cpu.94_1->c_bsp_resume, _2
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
.loc 1 1869 5 view .LVU75
testq %rax, %rax # _2
je .L8 #,
.loc 1 1870 3 is_stmt 1 view .LVU76
movq $boot_cpu_data, %rdi #,
jmp __x86_indirect_thunk_rax
or
.loc 2 57 9 view .LVU478
.loc 2 57 9 view .LVU479
.loc 2 57 9 view .LVU480
.loc 2 57 9 view .LVU481
.LBB1385:
.LBB1383:
.LBB1379:
.LBB1377:
.LBB1375:
.loc 2 57 9 view .LVU482
.loc 2 57 9 view .LVU483
movl %edi, %edx # cpu, cpu
.LVL87:
.loc 2 57 9 is_stmt 0 view .LVU484
That MOV in there is drowned in debugging information and latter makes
it hard to follow the asm. And that DWARF info is not really needed for
asm output staring.
Disable the debug information generation which clutters the asm output
unnecessarily:
bsp_resume:
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
movq this_cpu(%rip), %rax # this_cpu, this_cpu
movq 64(%rax), %rax # this_cpu.94_1->c_bsp_resume, _2
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
testq %rax, %rax # _2
je .L8 #,
# arch/x86/kernel/cpu/common.c:1870: this_cpu->c_bsp_resume(&boot_cpu_data);
movq $boot_cpu_data, %rdi #,
jmp __x86_indirect_thunk_rax
.L8:
# arch/x86/kernel/cpu/common.c:1871: }
rep ret
.size bsp_resume, .-bsp_resume
[ bp: write commit message. ]
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
2019-02-10 06:51:00 +00:00
|
|
|
DEBUG_CFLAGS += -g
|
2014-07-30 18:50:18 +00:00
|
|
|
endif
|
2014-02-14 23:19:17 +00:00
|
|
|
KBUILD_AFLAGS += -Wa,-gdwarf-2
|
2005-04-16 22:20:36 +00:00
|
|
|
endif
|
2014-07-30 18:50:19 +00:00
|
|
|
ifdef CONFIG_DEBUG_INFO_DWARF4
|
2019-02-22 07:56:09 +00:00
|
|
|
DEBUG_CFLAGS += -gdwarf-4
|
2014-07-30 18:50:19 +00:00
|
|
|
endif
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2010-07-14 13:43:52 +00:00
|
|
|
ifdef CONFIG_DEBUG_INFO_REDUCED
|
kbuild: Disable extra debugging info in .s output
Modern gcc adds view assignments, reset assertion checking in .loc
directives and a couple more additional debug markers, which clutters
the asm output unnecessarily:
For example:
bsp_resume:
.LFB3466:
.loc 1 1868 1 is_stmt 1 view -0
.cfi_startproc
.loc 1 1869 2 view .LVU73
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
.loc 1 1869 14 is_stmt 0 view .LVU74
movq this_cpu(%rip), %rax # this_cpu, this_cpu
movq 64(%rax), %rax # this_cpu.94_1->c_bsp_resume, _2
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
.loc 1 1869 5 view .LVU75
testq %rax, %rax # _2
je .L8 #,
.loc 1 1870 3 is_stmt 1 view .LVU76
movq $boot_cpu_data, %rdi #,
jmp __x86_indirect_thunk_rax
or
.loc 2 57 9 view .LVU478
.loc 2 57 9 view .LVU479
.loc 2 57 9 view .LVU480
.loc 2 57 9 view .LVU481
.LBB1385:
.LBB1383:
.LBB1379:
.LBB1377:
.LBB1375:
.loc 2 57 9 view .LVU482
.loc 2 57 9 view .LVU483
movl %edi, %edx # cpu, cpu
.LVL87:
.loc 2 57 9 is_stmt 0 view .LVU484
That MOV in there is drowned in debugging information and latter makes
it hard to follow the asm. And that DWARF info is not really needed for
asm output staring.
Disable the debug information generation which clutters the asm output
unnecessarily:
bsp_resume:
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
movq this_cpu(%rip), %rax # this_cpu, this_cpu
movq 64(%rax), %rax # this_cpu.94_1->c_bsp_resume, _2
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
testq %rax, %rax # _2
je .L8 #,
# arch/x86/kernel/cpu/common.c:1870: this_cpu->c_bsp_resume(&boot_cpu_data);
movq $boot_cpu_data, %rdi #,
jmp __x86_indirect_thunk_rax
.L8:
# arch/x86/kernel/cpu/common.c:1871: }
rep ret
.size bsp_resume, .-bsp_resume
[ bp: write commit message. ]
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
2019-02-10 06:51:00 +00:00
|
|
|
DEBUG_CFLAGS += $(call cc-option, -femit-struct-debug-baseonly) \
|
2013-02-07 21:58:40 +00:00
|
|
|
$(call cc-option,-fno-var-tracking)
|
2010-07-14 13:43:52 +00:00
|
|
|
endif
|
|
|
|
|
|
2020-05-26 17:18:29 +00:00
|
|
|
ifdef CONFIG_DEBUG_INFO_COMPRESSED
|
|
|
|
|
DEBUG_CFLAGS += -gz=zlib
|
Makefile: Improve compressed debug info support detection
Commit
10e68b02c861 ("Makefile: support compressed debug info")
added support for compressed debug sections.
Support is detected by checking
- does the compiler support -gz=zlib
- does the assembler support --compressed-debug-sections=zlib
- does the linker support --compressed-debug-sections=zlib
However, the gcc driver's support for this option is somewhat
convoluted. The driver's builtin specs are set based on the version of
binutils that it was configured with. It reports an error if the
configure-time linker/assembler (i.e., not necessarily the actual
assembler that will be run) do not support the option, but only if the
assembler (or linker) is actually invoked when -gz=zlib is passed.
The cc-option check in scripts/Kconfig.include does not invoke the
assembler, so the gcc driver reports success even if it does not support
the option being passed to the assembler.
Because the as-option check passes the option directly to the assembler
via -Wa,--compressed-debug-sections=zlib, the gcc driver does not see
this option and will never report an error.
Combined with an installed version of binutils that is more recent than
the one the compiler was built with, it is possible for all three tests
to succeed, yet an actual compilation with -gz=zlib to fail.
Moreover, it is unnecessary to explicitly pass
--compressed-debug-sections=zlib to the assembler via -Wa, since the
driver will do that automatically when it supports -gz=zlib.
Convert the as-option to just -gz=zlib, simplifying it as well as
performing a better test of the gcc driver's capabilities.
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Arvind Sankar <nivedita@alum.mit.edu>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2020-06-11 22:03:39 +00:00
|
|
|
KBUILD_AFLAGS += -gz=zlib
|
2020-05-26 17:18:29 +00:00
|
|
|
KBUILD_LDFLAGS += --compress-debug-sections=zlib
|
|
|
|
|
endif
|
|
|
|
|
|
kbuild: Disable extra debugging info in .s output
Modern gcc adds view assignments, reset assertion checking in .loc
directives and a couple more additional debug markers, which clutters
the asm output unnecessarily:
For example:
bsp_resume:
.LFB3466:
.loc 1 1868 1 is_stmt 1 view -0
.cfi_startproc
.loc 1 1869 2 view .LVU73
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
.loc 1 1869 14 is_stmt 0 view .LVU74
movq this_cpu(%rip), %rax # this_cpu, this_cpu
movq 64(%rax), %rax # this_cpu.94_1->c_bsp_resume, _2
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
.loc 1 1869 5 view .LVU75
testq %rax, %rax # _2
je .L8 #,
.loc 1 1870 3 is_stmt 1 view .LVU76
movq $boot_cpu_data, %rdi #,
jmp __x86_indirect_thunk_rax
or
.loc 2 57 9 view .LVU478
.loc 2 57 9 view .LVU479
.loc 2 57 9 view .LVU480
.loc 2 57 9 view .LVU481
.LBB1385:
.LBB1383:
.LBB1379:
.LBB1377:
.LBB1375:
.loc 2 57 9 view .LVU482
.loc 2 57 9 view .LVU483
movl %edi, %edx # cpu, cpu
.LVL87:
.loc 2 57 9 is_stmt 0 view .LVU484
That MOV in there is drowned in debugging information and latter makes
it hard to follow the asm. And that DWARF info is not really needed for
asm output staring.
Disable the debug information generation which clutters the asm output
unnecessarily:
bsp_resume:
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
movq this_cpu(%rip), %rax # this_cpu, this_cpu
movq 64(%rax), %rax # this_cpu.94_1->c_bsp_resume, _2
# arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
testq %rax, %rax # _2
je .L8 #,
# arch/x86/kernel/cpu/common.c:1870: this_cpu->c_bsp_resume(&boot_cpu_data);
movq $boot_cpu_data, %rdi #,
jmp __x86_indirect_thunk_rax
.L8:
# arch/x86/kernel/cpu/common.c:1871: }
rep ret
.size bsp_resume, .-bsp_resume
[ bp: write commit message. ]
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
2019-02-10 06:51:00 +00:00
|
|
|
KBUILD_CFLAGS += $(DEBUG_CFLAGS)
|
|
|
|
|
export DEBUG_CFLAGS
|
|
|
|
|
|
2008-10-06 23:06:12 +00:00
|
|
|
ifdef CONFIG_FUNCTION_TRACER
|
2018-08-06 13:17:44 +00:00
|
|
|
ifdef CONFIG_FTRACE_MCOUNT_RECORD
|
|
|
|
|
# gcc 5 supports generating the mcount tables directly
|
|
|
|
|
ifeq ($(call cc-option-yn,-mrecord-mcount),y)
|
|
|
|
|
CC_FLAGS_FTRACE += -mrecord-mcount
|
|
|
|
|
export CC_USING_RECORD_MCOUNT := 1
|
|
|
|
|
endif
|
2018-08-06 13:17:46 +00:00
|
|
|
ifdef CONFIG_HAVE_NOP_MCOUNT
|
|
|
|
|
ifeq ($(call cc-option-yn, -mnop-mcount),y)
|
|
|
|
|
CC_FLAGS_FTRACE += -mnop-mcount
|
|
|
|
|
CC_FLAGS_USING += -DCC_USING_NOP_MCOUNT
|
|
|
|
|
endif
|
|
|
|
|
endif
|
2018-08-06 13:17:44 +00:00
|
|
|
endif
|
2011-02-09 18:15:59 +00:00
|
|
|
ifdef CONFIG_HAVE_FENTRY
|
2018-08-06 13:17:42 +00:00
|
|
|
ifeq ($(call cc-option-yn, -mfentry),y)
|
|
|
|
|
CC_FLAGS_FTRACE += -mfentry
|
|
|
|
|
CC_FLAGS_USING += -DCC_USING_FENTRY
|
|
|
|
|
endif
|
2011-02-09 18:15:59 +00:00
|
|
|
endif
|
2018-08-06 13:17:42 +00:00
|
|
|
export CC_FLAGS_FTRACE
|
|
|
|
|
KBUILD_CFLAGS += $(CC_FLAGS_FTRACE) $(CC_FLAGS_USING)
|
|
|
|
|
KBUILD_AFLAGS += $(CC_FLAGS_USING)
|
2010-10-13 21:12:30 +00:00
|
|
|
ifdef CONFIG_DYNAMIC_FTRACE
|
2010-10-15 03:32:44 +00:00
|
|
|
ifdef CONFIG_HAVE_C_RECORDMCOUNT
|
2010-10-13 21:12:30 +00:00
|
|
|
BUILD_C_RECORDMCOUNT := y
|
|
|
|
|
export BUILD_C_RECORDMCOUNT
|
|
|
|
|
endif
|
|
|
|
|
endif
|
2008-05-12 19:20:42 +00:00
|
|
|
endif
|
|
|
|
|
|
2008-01-21 20:31:44 +00:00
|
|
|
# We trigger additional mismatches with less inlining
|
|
|
|
|
ifdef CONFIG_DEBUG_SECTION_MISMATCH
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option, -fno-inline-functions-called-once)
|
|
|
|
|
endif
|
|
|
|
|
|
2017-04-14 06:17:26 +00:00
|
|
|
ifdef CONFIG_LD_DEAD_CODE_DATA_ELIMINATION
|
2018-08-22 13:51:09 +00:00
|
|
|
KBUILD_CFLAGS_KERNEL += -ffunction-sections -fdata-sections
|
|
|
|
|
LDFLAGS_vmlinux += --gc-sections
|
2017-04-14 06:17:26 +00:00
|
|
|
endif
|
|
|
|
|
|
2019-04-04 18:44:11 +00:00
|
|
|
ifdef CONFIG_LIVEPATCH
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option, -flive-patching=inline-clone)
|
|
|
|
|
endif
|
|
|
|
|
|
2020-04-27 16:00:07 +00:00
|
|
|
ifdef CONFIG_SHADOW_CALL_STACK
|
|
|
|
|
CC_FLAGS_SCS := -fsanitize=shadow-call-stack
|
|
|
|
|
KBUILD_CFLAGS += $(CC_FLAGS_SCS)
|
|
|
|
|
export CC_FLAGS_SCS
|
|
|
|
|
endif
|
|
|
|
|
|
2005-04-30 23:51:42 +00:00
|
|
|
# arch Makefile may override CC so keep this after arch Makefile is included
|
kbuild: remove kbuild cache
The kbuild cache was introduced to remember the result of shell
commands, some of which are expensive to compute, such as
$(call cc-option,...).
However, this turned out not so clever as I had first expected.
Actually, it is problematic. For example, "$(CC) -print-file-name"
is cached. If the compiler is updated, the stale search path causes
build error, which is difficult to figure out. Another problem
scenario is cache files could be touched while install targets are
running under the root permission. We can patch them if desired,
but the build infrastructure is getting uglier and uglier.
Now, we are going to move compiler flag tests to the configuration
phase. If this is completed, the result of compiler tests will be
naturally cached in the .config file. We will not have performance
issues of incremental building since this testing only happens at
Kconfig time.
To start this work with a cleaner code base, remove the kbuild
cache first.
Revert the following commits:
Commit 9a234a2e3843 ("kbuild: create directory for make cache only when necessary")
Commit e17c400ae194 ("kbuild: shrink .cache.mk when it exceeds 1000 lines")
Commit 4e56207130ed ("kbuild: Cache a few more calls to the compiler")
Commit 3298b690b21c ("kbuild: Add a cache for generated variables")
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
2018-05-28 09:21:38 +00:00
|
|
|
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)
|
2005-04-30 23:51:42 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# warn about C99 declaration after statement
|
2018-10-01 09:44:37 +00:00
|
|
|
KBUILD_CFLAGS += -Wdeclaration-after-statement
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-06-25 22:59:34 +00:00
|
|
|
# Variable Length Arrays (VLAs) should not be used anywhere in the kernel
|
2019-05-09 06:45:49 +00:00
|
|
|
KBUILD_CFLAGS += -Wvla
|
2018-06-25 22:59:34 +00:00
|
|
|
|
2006-06-24 22:07:55 +00:00
|
|
|
# disable pointer signed / unsigned warnings in gcc 4.0
|
2018-10-01 09:44:36 +00:00
|
|
|
KBUILD_CFLAGS += -Wno-pointer-sign
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-08-30 21:47:28 +00:00
|
|
|
# disable stringop warnings in gcc 8+
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, stringop-truncation)
|
|
|
|
|
|
2020-05-09 21:30:29 +00:00
|
|
|
# We'll want to enable this eventually, but it's not going away for 5.7 at least
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, zero-length-bounds)
|
gcc-10: disable 'array-bounds' warning for now
This is another fine warning, related to the 'zero-length-bounds' one,
but hitting the same historical code in the kernel.
Because C didn't historically support flexible array members, we have
code that instead uses a one-sized array, the same way we have cases of
zero-sized arrays.
The one-sized arrays come from either not wanting to use the gcc
zero-sized array extension, or from a slight convenience-feature, where
particularly for strings, the size of the structure now includes the
allocation for the final NUL character.
So with a "char name[1];" at the end of a structure, you can do things
like
v = my_malloc(sizeof(struct vendor) + strlen(name));
and avoid the "+1" for the terminator.
Yes, the modern way to do that is with a flexible array, and using
'offsetof()' instead of 'sizeof()', and adding the "+1" by hand. That
also technically gets the size "more correct" in that it avoids any
alignment (and thus padding) issues, but this is another long-term
cleanup thing that will not happen for 5.7.
So disable the warning for now, even though it's potentially quite
useful. Having a slew of warnings that then hide more urgent new issues
is not an improvement.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2020-05-09 21:52:44 +00:00
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, array-bounds)
|
2020-05-09 22:40:52 +00:00
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, stringop-overflow)
|
2020-05-09 21:30:29 +00:00
|
|
|
|
gcc-10: disable 'restrict' warning for now
gcc-10 now warns about passing aliasing pointers to functions that take
restricted pointers.
That's actually a great warning, and if we ever start using 'restrict'
in the kernel, it might be quite useful. But right now we don't, and it
turns out that the only thing this warns about is an idiom where we have
declared a few functions to be "printf-like" (which seems to make gcc
pick up the restricted pointer thing), and then we print to the same
buffer that we also use as an input.
And people do that as an odd concatenation pattern, with code like this:
#define sysfs_show_gen_prop(buffer, fmt, ...) \
snprintf(buffer, PAGE_SIZE, "%s"fmt, buffer, __VA_ARGS__)
where we have 'buffer' as both the destination of the final result, and
as the initial argument.
Yes, it's a bit questionable. And outside of the kernel, people do have
standard declarations like
int snprintf( char *restrict buffer, size_t bufsz,
const char *restrict format, ... );
where that output buffer is marked as a restrict pointer that cannot
alias with any other arguments.
But in the context of the kernel, that 'use snprintf() to concatenate to
the end result' does work, and the pattern shows up in multiple places.
And we have not marked our own version of snprintf() as taking restrict
pointers, so the warning is incorrect for now, and gcc picks it up on
its own.
If we do start using 'restrict' in the kernel (and it might be a good
idea if people find places where it matters), we'll need to figure out
how to avoid this issue for snprintf and friends. But in the meantime,
this warning is not useful.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2020-05-09 22:45:21 +00:00
|
|
|
# Another good warning that we'll want to enable eventually
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, restrict)
|
|
|
|
|
|
Stop the ad-hoc games with -Wno-maybe-initialized
We have some rather random rules about when we accept the
"maybe-initialized" warnings, and when we don't.
For example, we consider it unreliable for gcc versions < 4.9, but also
if -O3 is enabled, or if optimizing for size. And then various kernel
config options disabled it, because they know that they trigger that
warning by confusing gcc sufficiently (ie PROFILE_ALL_BRANCHES).
And now gcc-10 seems to be introducing a lot of those warnings too, so
it falls under the same heading as 4.9 did.
At the same time, we have a very straightforward way to _enable_ that
warning when wanted: use "W=2" to enable more warnings.
So stop playing these ad-hoc games, and just disable that warning by
default, with the known and straight-forward "if you want to work on the
extra compiler warnings, use W=123".
Would it be great to have code that is always so obvious that it never
confuses the compiler whether a variable is used initialized or not?
Yes, it would. In a perfect world, the compilers would be smarter, and
our source code would be simpler.
That's currently not the world we live in, though.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2020-05-09 20:57:10 +00:00
|
|
|
# Enabled with W=2, disabled by default as noisy
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, maybe-uninitialized)
|
|
|
|
|
|
2009-04-09 11:34:34 +00:00
|
|
|
# disable invalid "can't wrap" optimizations for signed / pointers
|
2009-07-12 18:25:04 +00:00
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fno-strict-overflow)
|
2009-03-19 22:53:19 +00:00
|
|
|
|
kbuild: disable clang's default use of -fmerge-all-constants
Prasad reported that he has seen crashes in BPF subsystem with netd
on Android with arm64 in the form of (note, the taint is unrelated):
[ 4134.721483] Unable to handle kernel paging request at virtual address 800000001
[ 4134.820925] Mem abort info:
[ 4134.901283] Exception class = DABT (current EL), IL = 32 bits
[ 4135.016736] SET = 0, FnV = 0
[ 4135.119820] EA = 0, S1PTW = 0
[ 4135.201431] Data abort info:
[ 4135.301388] ISV = 0, ISS = 0x00000021
[ 4135.359599] CM = 0, WnR = 0
[ 4135.470873] user pgtable: 4k pages, 39-bit VAs, pgd = ffffffe39b946000
[ 4135.499757] [0000000800000001] *pgd=0000000000000000, *pud=0000000000000000
[ 4135.660725] Internal error: Oops: 96000021 [#1] PREEMPT SMP
[ 4135.674610] Modules linked in:
[ 4135.682883] CPU: 5 PID: 1260 Comm: netd Tainted: G S W 4.14.19+ #1
[ 4135.716188] task: ffffffe39f4aa380 task.stack: ffffff801d4e0000
[ 4135.731599] PC is at bpf_prog_add+0x20/0x68
[ 4135.741746] LR is at bpf_prog_inc+0x20/0x2c
[ 4135.751788] pc : [<ffffff94ab7ad584>] lr : [<ffffff94ab7ad638>] pstate: 60400145
[ 4135.769062] sp : ffffff801d4e3ce0
[...]
[ 4136.258315] Process netd (pid: 1260, stack limit = 0xffffff801d4e0000)
[ 4136.273746] Call trace:
[...]
[ 4136.442494] 3ca0: ffffff94ab7ad584 0000000060400145 ffffffe3a01bf8f8 0000000000000006
[ 4136.460936] 3cc0: 0000008000000000 ffffff94ab844204 ffffff801d4e3cf0 ffffff94ab7ad584
[ 4136.479241] [<ffffff94ab7ad584>] bpf_prog_add+0x20/0x68
[ 4136.491767] [<ffffff94ab7ad638>] bpf_prog_inc+0x20/0x2c
[ 4136.504536] [<ffffff94ab7b5d08>] bpf_obj_get_user+0x204/0x22c
[ 4136.518746] [<ffffff94ab7ade68>] SyS_bpf+0x5a8/0x1a88
Android's netd was basically pinning the uid cookie BPF map in BPF
fs (/sys/fs/bpf/traffic_cookie_uid_map) and later on retrieving it
again resulting in above panic. Issue is that the map was wrongly
identified as a prog! Above kernel was compiled with clang 4.0,
and it turns out that clang decided to merge the bpf_prog_iops and
bpf_map_iops into a single memory location, such that the two i_ops
could then not be distinguished anymore.
Reason for this miscompilation is that clang has the more aggressive
-fmerge-all-constants enabled by default. In fact, clang source code
has a comment about it in lib/AST/ExprConstant.cpp on why it is okay
to do so:
Pointers with different bases cannot represent the same object.
(Note that clang defaults to -fmerge-all-constants, which can
lead to inconsistent results for comparisons involving the address
of a constant; this generally doesn't matter in practice.)
The issue never appeared with gcc however, since gcc does not enable
-fmerge-all-constants by default and even *explicitly* states in
it's option description that using this flag results in non-conforming
behavior, quote from man gcc:
Languages like C or C++ require each variable, including multiple
instances of the same variable in recursive calls, to have distinct
locations, so using this option results in non-conforming behavior.
There are also various clang bug reports open on that matter [1],
where clang developers acknowledge the non-conforming behavior,
and refer to disabling it with -fno-merge-all-constants. But even
if this gets fixed in clang today, there are already users out there
that triggered this. Thus, fix this issue by explicitly adding
-fno-merge-all-constants to the kernel's Makefile to generically
disable this optimization, since potentially other places in the
kernel could subtly break as well.
Note, there is also a flag called -fmerge-constants (not supported
by clang), which is more conservative and only applies to strings
and it's enabled in gcc's -O/-O2/-O3/-Os optimization levels. In
gcc's code, the two flags -fmerge-{all-,}constants share the same
variable internally, so when disabling it via -fno-merge-all-constants,
then we really don't merge any const data (e.g. strings), and text
size increases with gcc (14,927,214 -> 14,942,646 for vmlinux.o).
$ gcc -fverbose-asm -O2 foo.c -S -o foo.S
-> foo.S lists -fmerge-constants under options enabled
$ gcc -fverbose-asm -O2 -fno-merge-all-constants foo.c -S -o foo.S
-> foo.S doesn't list -fmerge-constants under options enabled
$ gcc -fverbose-asm -O2 -fno-merge-all-constants -fmerge-constants foo.c -S -o foo.S
-> foo.S lists -fmerge-constants under options enabled
Thus, as a workaround we need to set both -fno-merge-all-constants
*and* -fmerge-constants in the Makefile in order for text size to
stay as is.
[1] https://bugs.llvm.org/show_bug.cgi?id=18538
Reported-by: Prasad Sodagudi <psodagud@codeaurora.org>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chenbo Feng <fengc@google.com>
Cc: Richard Smith <richard-llvm@metafoo.co.uk>
Cc: Chandler Carruth <chandlerc@gmail.com>
Cc: linux-kernel@vger.kernel.org
Tested-by: Prasad Sodagudi <psodagud@codeaurora.org>
Acked-by: Alexei Starovoitov <ast@kernel.org>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
2018-03-21 00:18:24 +00:00
|
|
|
# clang sets -fmerge-all-constants by default as optimization, but this
|
|
|
|
|
# is non-conforming behavior for C and in fact breaks the kernel, so we
|
|
|
|
|
# need to disable it here generally.
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fno-merge-all-constants)
|
|
|
|
|
|
|
|
|
|
# for gcc -fno-merge-all-constants disables everything, but it is fine
|
|
|
|
|
# to have actual conforming behavior enabled.
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fmerge-constants)
|
|
|
|
|
|
2017-12-30 01:34:43 +00:00
|
|
|
# Make sure -fstack-check isn't enabled (like gentoo apparently did)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fno-stack-check,)
|
|
|
|
|
|
2009-09-18 19:49:37 +00:00
|
|
|
# conserve stack if available
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fconserve-stack)
|
|
|
|
|
|
2013-12-23 21:56:06 +00:00
|
|
|
# Prohibit date/time macros, which would make the build non-deterministic
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Werror=date-time)
|
|
|
|
|
|
2016-03-08 08:29:09 +00:00
|
|
|
# enforce correct pointer usage
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Werror=incompatible-pointer-types)
|
|
|
|
|
|
2017-03-21 00:14:11 +00:00
|
|
|
# Require designated initializers for all marked structures
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Werror=designated-init)
|
|
|
|
|
|
2018-03-30 04:15:26 +00:00
|
|
|
# change __FILE__ to the relative path from the srctree
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fmacro-prefix-map=$(srctree)/=)
|
|
|
|
|
|
2019-07-17 16:06:26 +00:00
|
|
|
# ensure -fcf-protection is disabled when using retpoline as it is
|
|
|
|
|
# incompatible with -mindirect-branch=thunk-extern
|
|
|
|
|
ifdef CONFIG_RETPOLINE
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fcf-protection=none)
|
|
|
|
|
endif
|
|
|
|
|
|
2015-03-27 11:43:36 +00:00
|
|
|
include scripts/Makefile.kasan
|
|
|
|
|
include scripts/Makefile.extrawarn
|
2016-01-20 23:00:55 +00:00
|
|
|
include scripts/Makefile.ubsan
|
2019-11-14 18:02:54 +00:00
|
|
|
include scripts/Makefile.kcsan
|
2014-04-14 09:27:10 +00:00
|
|
|
|
2019-08-20 17:09:41 +00:00
|
|
|
# Add user supplied CPPFLAGS, AFLAGS and CFLAGS as the last assignments
|
|
|
|
|
KBUILD_CPPFLAGS += $(KCPPFLAGS)
|
|
|
|
|
KBUILD_AFLAGS += $(KAFLAGS)
|
|
|
|
|
KBUILD_CFLAGS += $(KCFLAGS)
|
2007-10-15 20:03:58 +00:00
|
|
|
|
2019-07-13 04:01:10 +00:00
|
|
|
KBUILD_LDFLAGS_MODULE += --build-id
|
|
|
|
|
LDFLAGS_vmlinux += --build-id
|
2007-07-19 08:48:40 +00:00
|
|
|
|
2009-03-04 19:59:07 +00:00
|
|
|
ifeq ($(CONFIG_STRIP_ASM_SYMS),y)
|
2009-09-16 20:36:55 +00:00
|
|
|
LDFLAGS_vmlinux += $(call ld-option, -X,)
|
2009-03-04 19:59:07 +00:00
|
|
|
endif
|
|
|
|
|
|
2019-08-01 01:18:42 +00:00
|
|
|
ifeq ($(CONFIG_RELR),y)
|
|
|
|
|
LDFLAGS_vmlinux += --pack-dyn-relocs=relr
|
|
|
|
|
endif
|
|
|
|
|
|
kbuild: add infrastructure to build userspace programs
Kbuild supports the infrastructure to build host programs, but there
was no support to build userspace programs for the target architecture
(i.e. the same architecture as the kernel).
Sam Ravnborg worked on this in 2014 (https://lkml.org/lkml/2014/7/13/154),
but it was not merged. One problem at that time was, there was no good way
to know whether $(CC) can link standalone programs. In fact, pre-built
kernel.org toolchains [1] are often used for building the kernel, but they
do not provide libc.
Now, we can handle this cleanly because the compiler capability is
evaluated at the Kconfig time. If $(CC) cannot link standalone programs,
the relevant options are hidden by 'depends on CC_CAN_LINK'.
The implementation just mimics scripts/Makefile.host
The userspace programs are compiled with the same flags as the host
programs. In addition, it uses -m32 or -m64 if it is found in
$(KBUILD_CFLAGS).
This new syntax has two usecases.
- Sample programs
Several userspace programs under samples/ include UAPI headers
installed in usr/include. Most of them were previously built for
the host architecture just to use the 'hostprogs' syntax.
However, 'make headers' always works for the target architecture.
This caused the arch mismatch in cross-compiling. To fix this
distortion, sample code should be built for the target architecture.
- Bpfilter
net/bpfilter/Makefile compiles bpfilter_umh as the user mode helper,
and embeds it into the kernel. Currently, it overrides HOSTCC with
CC to use the 'hostprogs' syntax. This hack should go away.
[1]: https://mirrors.edge.kernel.org/pub/tools/crosstool/
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
2020-04-29 03:45:14 +00:00
|
|
|
# Align the bit size of userspace programs with the kernel
|
|
|
|
|
KBUILD_USERCFLAGS += $(filter -m32 -m64, $(KBUILD_CFLAGS))
|
|
|
|
|
KBUILD_USERLDFLAGS += $(filter -m32 -m64, $(KBUILD_CFLAGS))
|
|
|
|
|
|
2019-11-09 12:12:16 +00:00
|
|
|
# make the checker run with the right architecture
|
|
|
|
|
CHECKFLAGS += --arch=$(ARCH)
|
|
|
|
|
|
2018-05-28 18:27:35 +00:00
|
|
|
# insure the checker run with the right endianness
|
|
|
|
|
CHECKFLAGS += $(if $(CONFIG_CPU_BIG_ENDIAN),-mbig-endian,-mlittle-endian)
|
|
|
|
|
|
2018-05-30 20:48:38 +00:00
|
|
|
# the checker needs the correct machine size
|
|
|
|
|
CHECKFLAGS += $(if $(CONFIG_64BIT),-m64,-m32)
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# Default kernel image to build when no specific target is given.
|
2006-06-24 22:07:55 +00:00
|
|
|
# KBUILD_IMAGE may be overruled on the command line or
|
2005-04-16 22:20:36 +00:00
|
|
|
# set in the environment
|
|
|
|
|
# Also any assignments in arch/$(ARCH)/Makefile take precedence over
|
|
|
|
|
# this default value
|
|
|
|
|
export KBUILD_IMAGE ?= vmlinux
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# INSTALL_PATH specifies where to place the updated kernel and system map
|
|
|
|
|
# images. Default is /boot, but you can set it to other values
|
|
|
|
|
export INSTALL_PATH ?= /boot
|
|
|
|
|
|
2013-12-01 23:56:28 +00:00
|
|
|
#
|
|
|
|
|
# INSTALL_DTBS_PATH specifies a prefix for relocations required by build roots.
|
|
|
|
|
# Like INSTALL_MOD_PATH, it isn't defined in the Makefile, but can be passed as
|
|
|
|
|
# an argument if needed. Otherwise it defaults to the kernel install path
|
|
|
|
|
#
|
|
|
|
|
export INSTALL_DTBS_PATH ?= $(INSTALL_PATH)/dtbs/$(KERNELRELEASE)
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
#
|
|
|
|
|
# INSTALL_MOD_PATH specifies a prefix to MODLIB for module directory
|
|
|
|
|
# relocations required by build roots. This is not defined in the
|
2006-06-24 22:07:55 +00:00
|
|
|
# makefile but the argument can be passed to make if needed.
|
2005-04-16 22:20:36 +00:00
|
|
|
#
|
|
|
|
|
|
2006-01-16 11:46:07 +00:00
|
|
|
MODLIB = $(INSTALL_MOD_PATH)/lib/modules/$(KERNELRELEASE)
|
2005-04-16 22:20:36 +00:00
|
|
|
export MODLIB
|
|
|
|
|
|
2006-06-22 00:53:09 +00:00
|
|
|
#
|
2014-04-28 07:32:43 +00:00
|
|
|
# INSTALL_MOD_STRIP, if defined, will cause modules to be
|
|
|
|
|
# stripped after they are installed. If INSTALL_MOD_STRIP is '1', then
|
|
|
|
|
# the default option --strip-debug will be used. Otherwise,
|
|
|
|
|
# INSTALL_MOD_STRIP value will be used as the options to the strip command.
|
2009-01-14 20:38:20 +00:00
|
|
|
|
2006-06-22 00:53:09 +00:00
|
|
|
ifdef INSTALL_MOD_STRIP
|
|
|
|
|
ifeq ($(INSTALL_MOD_STRIP),1)
|
2009-01-14 20:38:20 +00:00
|
|
|
mod_strip_cmd = $(STRIP) --strip-debug
|
2006-06-22 00:53:09 +00:00
|
|
|
else
|
2009-01-14 20:38:20 +00:00
|
|
|
mod_strip_cmd = $(STRIP) $(INSTALL_MOD_STRIP)
|
2006-06-22 00:53:09 +00:00
|
|
|
endif # INSTALL_MOD_STRIP=1
|
|
|
|
|
else
|
2009-01-14 20:38:20 +00:00
|
|
|
mod_strip_cmd = true
|
2006-06-22 00:53:09 +00:00
|
|
|
endif # INSTALL_MOD_STRIP
|
|
|
|
|
export mod_strip_cmd
|
|
|
|
|
|
2014-08-27 11:01:56 +00:00
|
|
|
# CONFIG_MODULE_COMPRESS, if defined, will cause module to be compressed
|
|
|
|
|
# after they are installed in agreement with CONFIG_MODULE_COMPRESS_GZIP
|
|
|
|
|
# or CONFIG_MODULE_COMPRESS_XZ.
|
|
|
|
|
|
|
|
|
|
mod_compress_cmd = true
|
|
|
|
|
ifdef CONFIG_MODULE_COMPRESS
|
|
|
|
|
ifdef CONFIG_MODULE_COMPRESS_GZIP
|
kbuild: fix broken builds because of GZIP,BZIP2,LZOP variables
Redefine GZIP, BZIP2, LZOP variables as KGZIP, KBZIP2, KLZOP resp.
GZIP, BZIP2, LZOP env variables are reserved by the tools. The original
attempt to redefine them internally doesn't work in makefiles/scripts
intercall scenarios, e.g., "make GZIP=gzip bindeb-pkg" and results in
broken builds. There can be other broken build commands because of this,
so the universal solution is to use non-reserved env variables for the
compression tools.
Fixes: 8dfb61dcbace ("kbuild: add variables for compression tools")
Signed-off-by: Denis Efremov <efremov@linux.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2020-06-08 09:59:44 +00:00
|
|
|
mod_compress_cmd = $(KGZIP) -n -f
|
2014-08-27 11:01:56 +00:00
|
|
|
endif # CONFIG_MODULE_COMPRESS_GZIP
|
|
|
|
|
ifdef CONFIG_MODULE_COMPRESS_XZ
|
kbuild: add variables for compression tools
Allow user to use alternative implementations of compression tools,
such as pigz, pbzip2, pxz. For example, multi-threaded tools to
speed up the build:
$ make GZIP=pigz BZIP2=pbzip2
Variables _GZIP, _BZIP2, _LZOP are used internally because original env
vars are reserved by the tools. The use of GZIP in gzip tool is obsolete
since 2015. However, alternative implementations (e.g., pigz) still rely
on it. BZIP2, BZIP, LZOP vars are not obsolescent.
The credit goes to @grsecurity.
As a sidenote, for multi-threaded lzma, xz compression one can use:
$ export XZ_OPT="--threads=0"
Signed-off-by: Denis Efremov <efremov@linux.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2020-06-05 07:39:55 +00:00
|
|
|
mod_compress_cmd = $(XZ) -f
|
2014-08-27 11:01:56 +00:00
|
|
|
endif # CONFIG_MODULE_COMPRESS_XZ
|
|
|
|
|
endif # CONFIG_MODULE_COMPRESS
|
|
|
|
|
export mod_compress_cmd
|
|
|
|
|
|
2013-01-25 03:11:31 +00:00
|
|
|
ifdef CONFIG_MODULE_SIG_ALL
|
2015-08-14 15:17:16 +00:00
|
|
|
$(eval $(call config_filename,MODULE_SIG_KEY))
|
|
|
|
|
|
|
|
|
|
mod_sign_cmd = scripts/sign-file $(CONFIG_MODULE_SIG_HASH) $(MODULE_SIG_KEY_SRCPREFIX)$(CONFIG_MODULE_SIG_KEY) certs/signing_key.x509
|
2012-10-19 01:23:15 +00:00
|
|
|
else
|
|
|
|
|
mod_sign_cmd = true
|
|
|
|
|
endif
|
|
|
|
|
export mod_sign_cmd
|
|
|
|
|
|
2019-03-26 17:48:39 +00:00
|
|
|
HOST_LIBELF_LIBS = $(shell pkg-config libelf --libs 2>/dev/null || echo -lelf)
|
|
|
|
|
|
2017-02-15 18:21:17 +00:00
|
|
|
ifdef CONFIG_STACK_VALIDATION
|
|
|
|
|
has_libelf := $(call try-run,\
|
2019-03-26 17:48:39 +00:00
|
|
|
echo "int main() {}" | $(HOSTCC) -xc -o /dev/null $(HOST_LIBELF_LIBS) -,1,0)
|
2017-02-15 18:21:17 +00:00
|
|
|
ifeq ($(has_libelf),1)
|
|
|
|
|
objtool_target := tools/objtool FORCE
|
|
|
|
|
else
|
|
|
|
|
SKIP_STACK_VALIDATION := 1
|
|
|
|
|
export SKIP_STACK_VALIDATION
|
|
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
2019-01-15 07:19:00 +00:00
|
|
|
PHONY += prepare0
|
2012-10-19 01:23:15 +00:00
|
|
|
|
kbuild: make single targets work more correctly
Currently, the single target build directly descends into the directory
of the target. For example,
$ make foo/bar/baz.o
... directly descends into foo/bar/.
On the other hand, the normal build usually descends one directory at
a time, i.e. descends into foo/, and then foo/bar/.
This difference causes some problems.
[1] miss subdir-asflags-y, subdir-ccflags-y in upper Makefiles
The options in subdir-{as,cc}flags-y take effect in the current
and its sub-directories. In other words, they are inherited
downward. In the example above, the single target will miss
subdir-{as,cc}flags-y if they are defined in foo/Makefile.
[2] could be built in a different directory
As Documentation/kbuild/modules.rst section 4.3 says, Kbuild can
handle files that are spread over several sub-directories.
The build rule of foo/bar/baz.o may not necessarily be specified in
foo/bar/Makefile. It might be specifies in foo/Makefile as follows:
[foo/Makefile]
obj-y := bar/baz.o
This often happens when a module is so big that its source files
are divided into sub-directories.
In this case, there is no Makefile in the foo/bar/ directory, yet
the single target descends into foo/bar/, then fails due to the
missing Makefile. You can still do 'make foo/bar/' for partial
building, but cannot do 'make foo/bar/baz.s'. I believe the single
target '%.s' is a useful feature for inspecting the compiler output.
Some modules work around this issue by putting an empty Makefile
in every sub-directory.
This commit fixes those problems by making the single target build
descend in the same way as the normal build does.
Another change is the single target build will observe the CONFIG
options. Previously, it allowed users to build the foo.o even when
the corresponding CONFIG_FOO is disabled:
obj-$(CONFIG_FOO) += foo.o
In the new behavior, the single target build will just fail and show
"No rule to make target ..." (or "Nothing to be done for ..." if the
stale object already exists, but cannot be updated).
The disadvantage of this commit is the build speed. Now that the
single target build visits every directory and parses lots of
Makefiles, it is slower than before. (But, I hope it will not be
too slow.)
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-08-14 15:19:18 +00:00
|
|
|
export MODORDER := $(extmod-prefix)modules.order
|
2019-10-29 12:38:08 +00:00
|
|
|
export MODULES_NSDEPS := $(extmod-prefix)modules.nsdeps
|
2019-08-02 10:23:58 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
2015-08-14 14:20:41 +00:00
|
|
|
core-y += kernel/ certs/ mm/ fs/ ipc/ security/ crypto/ block/
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-06-01 05:56:57 +00:00
|
|
|
vmlinux-dirs := $(patsubst %/,%,$(filter %/, \
|
2005-04-16 22:20:36 +00:00
|
|
|
$(core-y) $(core-m) $(drivers-y) $(drivers-m) \
|
2020-06-01 05:56:58 +00:00
|
|
|
$(libs-y) $(libs-m)))
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-04-27 03:33:37 +00:00
|
|
|
vmlinux-alldirs := $(sort $(vmlinux-dirs) Documentation \
|
2020-06-01 05:56:57 +00:00
|
|
|
$(patsubst %/,%,$(filter %/, $(core-) \
|
2020-06-01 05:56:58 +00:00
|
|
|
$(drivers-) $(libs-))))
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-06-01 05:57:00 +00:00
|
|
|
subdir-modorder := $(addsuffix modules.order,$(filter %/, \
|
|
|
|
|
$(core-y) $(core-m) $(libs-y) $(libs-m) \
|
|
|
|
|
$(drivers-y) $(drivers-m)))
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-08-10 15:53:04 +00:00
|
|
|
build-dirs := $(vmlinux-dirs)
|
2019-08-10 15:53:05 +00:00
|
|
|
clean-dirs := $(vmlinux-alldirs)
|
2019-08-10 15:53:04 +00:00
|
|
|
|
2020-06-01 05:56:59 +00:00
|
|
|
# Externally visible symbols (used by link-vmlinux.sh)
|
|
|
|
|
KBUILD_VMLINUX_OBJS := $(head-y) $(patsubst %/,%/built-in.a, $(core-y))
|
|
|
|
|
KBUILD_VMLINUX_OBJS += $(addsuffix built-in.a, $(filter %/, $(libs-y)))
|
kbuild: link lib-y objects to vmlinux forcibly when CONFIG_MODULES=y
Kbuild supports not only obj-y but also lib-y to list objects linked to
vmlinux.
The difference between them is that all the objects from obj-y are
forcibly linked to vmlinux, whereas the objects from lib-y are linked
as needed; if there is no user of a lib-y object, it is not linked.
lib-y is intended to list utility functions that may be called from all
over the place (and may be unused at all), but it is a problem for
EXPORT_SYMBOL(). Even if there is no call-site in the vmlinux, we need
to keep exported symbols for the use from loadable modules.
Commit 7f2084fa55e6 ("[kbuild] handle exports in lib-y objects reliably")
worked around it by linking a dummy object, lib-ksyms.o, which contains
references to all the symbols exported from lib.a in that directory.
It uses the linker script command, EXTERN. Unfortunately, the meaning of
EXTERN of ld.lld is different from that of ld.bfd. Therefore, this does
not work with LD=ld.lld (CBL issue #515).
Anyway, the build rule of lib-ksyms.o is somewhat tricky. So, I want to
get rid of it.
At first, I was thinking of accumulating lib-y objects into obj-y
(or even replacing lib-y with obj-y entirely), but the lib-y syntax
is used beyond the ordinary use in lib/ and arch/*/lib/.
Examples:
- drivers/firmware/efi/libstub/Makefile builds lib.a, which is linked
into vmlinux in the own way (arm64), or linked to the decompressor
(arm, x86).
- arch/alpha/lib/Makefile builds lib.a which is linked not only to
vmlinux, but also to bootloaders in arch/alpha/boot/Makefile.
- arch/xtensa/boot/lib/Makefile builds lib.a for use from
arch/xtensa/boot/boot-redboot/Makefile.
One more thing, adding everything to obj-y would increase the vmlinux
size of allnoconfig (or tinyconfig).
For less impact, I tweaked the destination of lib.a at the top Makefile;
when CONFIG_MODULES=y, lib.a goes to KBUILD_VMLINUX_OBJS, which is
forcibly linked to vmlinux, otherwise lib.a goes to KBUILD_VMLINUX_LIBS
as before.
The size impact for normal usecases is quite small since at lease one
symbol in every lib-y object is eventually called by someone. In case
you are intrested, here are the figures.
x86_64_defconfig:
text data bss dec hex filename
19566602 5422072 1589328 26578002 1958c52 vmlinux.before
19566932 5422104 1589328 26578364 1958dbc vmlinux.after
The case with the biggest impact is allnoconfig + CONFIG_MODULES=y.
ARCH=x86 allnoconfig + CONFIG_MODULES=y:
text data bss dec hex filename
1175162 254740 1220608 2650510 28718e vmlinux.before
1177974 254836 1220608 2653418 287cea vmlinux.after
Hopefully this is still not a big deal. The per-file trimming with the
static library is not so effective after all.
If fine-grained optimization is desired, some architectures support
CONFIG_LD_DEAD_CODE_DATA_ELIMINATION, which trims dead code per-symbol
basis. When LTO is supported in mainline, even better optimization will
be possible.
Link: https://github.com/ClangBuiltLinux/linux/issues/515
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reported-by: kbuild test robot <lkp@intel.com>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
2020-03-11 22:37:25 +00:00
|
|
|
ifdef CONFIG_MODULES
|
2020-06-01 05:56:59 +00:00
|
|
|
KBUILD_VMLINUX_OBJS += $(patsubst %/, %/lib.a, $(filter %/, $(libs-y)))
|
|
|
|
|
KBUILD_VMLINUX_LIBS := $(filter-out %/, $(libs-y))
|
kbuild: link lib-y objects to vmlinux forcibly when CONFIG_MODULES=y
Kbuild supports not only obj-y but also lib-y to list objects linked to
vmlinux.
The difference between them is that all the objects from obj-y are
forcibly linked to vmlinux, whereas the objects from lib-y are linked
as needed; if there is no user of a lib-y object, it is not linked.
lib-y is intended to list utility functions that may be called from all
over the place (and may be unused at all), but it is a problem for
EXPORT_SYMBOL(). Even if there is no call-site in the vmlinux, we need
to keep exported symbols for the use from loadable modules.
Commit 7f2084fa55e6 ("[kbuild] handle exports in lib-y objects reliably")
worked around it by linking a dummy object, lib-ksyms.o, which contains
references to all the symbols exported from lib.a in that directory.
It uses the linker script command, EXTERN. Unfortunately, the meaning of
EXTERN of ld.lld is different from that of ld.bfd. Therefore, this does
not work with LD=ld.lld (CBL issue #515).
Anyway, the build rule of lib-ksyms.o is somewhat tricky. So, I want to
get rid of it.
At first, I was thinking of accumulating lib-y objects into obj-y
(or even replacing lib-y with obj-y entirely), but the lib-y syntax
is used beyond the ordinary use in lib/ and arch/*/lib/.
Examples:
- drivers/firmware/efi/libstub/Makefile builds lib.a, which is linked
into vmlinux in the own way (arm64), or linked to the decompressor
(arm, x86).
- arch/alpha/lib/Makefile builds lib.a which is linked not only to
vmlinux, but also to bootloaders in arch/alpha/boot/Makefile.
- arch/xtensa/boot/lib/Makefile builds lib.a for use from
arch/xtensa/boot/boot-redboot/Makefile.
One more thing, adding everything to obj-y would increase the vmlinux
size of allnoconfig (or tinyconfig).
For less impact, I tweaked the destination of lib.a at the top Makefile;
when CONFIG_MODULES=y, lib.a goes to KBUILD_VMLINUX_OBJS, which is
forcibly linked to vmlinux, otherwise lib.a goes to KBUILD_VMLINUX_LIBS
as before.
The size impact for normal usecases is quite small since at lease one
symbol in every lib-y object is eventually called by someone. In case
you are intrested, here are the figures.
x86_64_defconfig:
text data bss dec hex filename
19566602 5422072 1589328 26578002 1958c52 vmlinux.before
19566932 5422104 1589328 26578364 1958dbc vmlinux.after
The case with the biggest impact is allnoconfig + CONFIG_MODULES=y.
ARCH=x86 allnoconfig + CONFIG_MODULES=y:
text data bss dec hex filename
1175162 254740 1220608 2650510 28718e vmlinux.before
1177974 254836 1220608 2653418 287cea vmlinux.after
Hopefully this is still not a big deal. The per-file trimming with the
static library is not so effective after all.
If fine-grained optimization is desired, some architectures support
CONFIG_LD_DEAD_CODE_DATA_ELIMINATION, which trims dead code per-symbol
basis. When LTO is supported in mainline, even better optimization will
be possible.
Link: https://github.com/ClangBuiltLinux/linux/issues/515
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reported-by: kbuild test robot <lkp@intel.com>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
2020-03-11 22:37:25 +00:00
|
|
|
else
|
2020-06-01 05:56:59 +00:00
|
|
|
KBUILD_VMLINUX_LIBS := $(patsubst %/,%/lib.a, $(libs-y))
|
kbuild: link lib-y objects to vmlinux forcibly when CONFIG_MODULES=y
Kbuild supports not only obj-y but also lib-y to list objects linked to
vmlinux.
The difference between them is that all the objects from obj-y are
forcibly linked to vmlinux, whereas the objects from lib-y are linked
as needed; if there is no user of a lib-y object, it is not linked.
lib-y is intended to list utility functions that may be called from all
over the place (and may be unused at all), but it is a problem for
EXPORT_SYMBOL(). Even if there is no call-site in the vmlinux, we need
to keep exported symbols for the use from loadable modules.
Commit 7f2084fa55e6 ("[kbuild] handle exports in lib-y objects reliably")
worked around it by linking a dummy object, lib-ksyms.o, which contains
references to all the symbols exported from lib.a in that directory.
It uses the linker script command, EXTERN. Unfortunately, the meaning of
EXTERN of ld.lld is different from that of ld.bfd. Therefore, this does
not work with LD=ld.lld (CBL issue #515).
Anyway, the build rule of lib-ksyms.o is somewhat tricky. So, I want to
get rid of it.
At first, I was thinking of accumulating lib-y objects into obj-y
(or even replacing lib-y with obj-y entirely), but the lib-y syntax
is used beyond the ordinary use in lib/ and arch/*/lib/.
Examples:
- drivers/firmware/efi/libstub/Makefile builds lib.a, which is linked
into vmlinux in the own way (arm64), or linked to the decompressor
(arm, x86).
- arch/alpha/lib/Makefile builds lib.a which is linked not only to
vmlinux, but also to bootloaders in arch/alpha/boot/Makefile.
- arch/xtensa/boot/lib/Makefile builds lib.a for use from
arch/xtensa/boot/boot-redboot/Makefile.
One more thing, adding everything to obj-y would increase the vmlinux
size of allnoconfig (or tinyconfig).
For less impact, I tweaked the destination of lib.a at the top Makefile;
when CONFIG_MODULES=y, lib.a goes to KBUILD_VMLINUX_OBJS, which is
forcibly linked to vmlinux, otherwise lib.a goes to KBUILD_VMLINUX_LIBS
as before.
The size impact for normal usecases is quite small since at lease one
symbol in every lib-y object is eventually called by someone. In case
you are intrested, here are the figures.
x86_64_defconfig:
text data bss dec hex filename
19566602 5422072 1589328 26578002 1958c52 vmlinux.before
19566932 5422104 1589328 26578364 1958dbc vmlinux.after
The case with the biggest impact is allnoconfig + CONFIG_MODULES=y.
ARCH=x86 allnoconfig + CONFIG_MODULES=y:
text data bss dec hex filename
1175162 254740 1220608 2650510 28718e vmlinux.before
1177974 254836 1220608 2653418 287cea vmlinux.after
Hopefully this is still not a big deal. The per-file trimming with the
static library is not so effective after all.
If fine-grained optimization is desired, some architectures support
CONFIG_LD_DEAD_CODE_DATA_ELIMINATION, which trims dead code per-symbol
basis. When LTO is supported in mainline, even better optimization will
be possible.
Link: https://github.com/ClangBuiltLinux/linux/issues/515
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reported-by: kbuild test robot <lkp@intel.com>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
2020-03-11 22:37:25 +00:00
|
|
|
endif
|
2020-06-01 05:56:59 +00:00
|
|
|
KBUILD_VMLINUX_OBJS += $(patsubst %/,%/built-in.a, $(drivers-y))
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-06-01 05:56:59 +00:00
|
|
|
export KBUILD_VMLINUX_OBJS KBUILD_VMLINUX_LIBS
|
2012-05-05 08:18:40 +00:00
|
|
|
export KBUILD_LDS := arch/$(SRCARCH)/kernel/vmlinux.lds
|
2012-05-05 08:18:41 +00:00
|
|
|
export LDFLAGS_vmlinux
|
2019-09-21 13:18:46 +00:00
|
|
|
# used by scripts/Makefile.package
|
2019-05-15 16:18:54 +00:00
|
|
|
export KBUILD_ALLDIRS := $(sort $(filter-out arch/%,$(vmlinux-alldirs)) LICENSES arch include scripts tools)
|
2008-12-16 11:30:08 +00:00
|
|
|
|
2019-01-17 00:10:04 +00:00
|
|
|
vmlinux-deps := $(KBUILD_LDS) $(KBUILD_VMLINUX_OBJS) $(KBUILD_VMLINUX_LIBS)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-03-16 07:37:15 +00:00
|
|
|
# Recurse until adjust_autoksyms.sh is satisfied
|
|
|
|
|
PHONY += autoksyms_recursive
|
2016-04-22 19:25:00 +00:00
|
|
|
ifdef CONFIG_TRIM_UNUSED_KSYMS
|
2018-03-16 07:37:13 +00:00
|
|
|
# For the kernel to actually contain only the needed exported symbols,
|
|
|
|
|
# we have to build modules as well to determine what those symbols are.
|
|
|
|
|
# (this can be evaluated only once include/config/auto.conf has been included)
|
2020-05-31 10:11:39 +00:00
|
|
|
KBUILD_MODULES := 1
|
|
|
|
|
|
|
|
|
|
autoksyms_recursive: descend modules.order
|
|
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/adjust_autoksyms.sh \
|
|
|
|
|
"$(MAKE) -f $(srctree)/Makefile vmlinux"
|
2018-03-16 07:37:13 +00:00
|
|
|
endif
|
|
|
|
|
|
kbuild: restore autoksyms.h touch to the top Makefile
Commit d3fc425e819b ("kbuild: make sure autoksyms.h exists early")
moved the code that touches autoksyms.h to scripts/kconfig/Makefile
with obscure reason.
From Nicolas' comment [1], he did not seem to be sure about the root
cause.
I guess I figured it out, so here is a fix-up I think is more correct.
According to the error log in the original post [2], the build failed
in scripts/mod/devicetable-offsets.c
scripts/mod/Makefile is descended from scripts/Makefile, which is
invoked from the top-level Makefile by the 'scripts' target.
To build vmlinux and/or modules, Kbuild descend into $(vmlinux-dirs).
This depends on 'prepare' and 'scripts' as follows:
$(vmlinux-dirs): prepare scripts
Because there is no dependency between 'prepare' and 'scripts', the
parallel building can execute them simultaneously.
'prepare' depends on 'prepare1', which touched autoksyms.h, while
'scripts' descends into script/, then scripts/mod/, which needs
<generated/autoksyms.h> if CONFIG_TRIM_UNUSED_KSYMS. It was the
reason of the race.
I am not happy to have unrelated code in the Kconfig Makefile, so
getting it back to the top Makefile.
I removed the standalone test target because I want to use it to
create an empty autoksyms.h file. Here is a little improvement;
unnecessary autoksyms.h is not created when CONFIG_TRIM_UNUSED_KSYMS
is disabled.
[1] https://lkml.org/lkml/2016/11/30/734
[2] https://lkml.org/lkml/2016/11/30/531
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Nicolas Pitre <nico@linaro.org>
2018-03-16 07:37:12 +00:00
|
|
|
autoksyms_h := $(if $(CONFIG_TRIM_UNUSED_KSYMS), include/generated/autoksyms.h)
|
|
|
|
|
|
2020-02-28 17:20:15 +00:00
|
|
|
quiet_cmd_autoksyms_h = GEN $@
|
|
|
|
|
cmd_autoksyms_h = mkdir -p $(dir $@); \
|
|
|
|
|
$(CONFIG_SHELL) $(srctree)/scripts/gen_autoksyms.sh $@
|
|
|
|
|
|
kbuild: restore autoksyms.h touch to the top Makefile
Commit d3fc425e819b ("kbuild: make sure autoksyms.h exists early")
moved the code that touches autoksyms.h to scripts/kconfig/Makefile
with obscure reason.
From Nicolas' comment [1], he did not seem to be sure about the root
cause.
I guess I figured it out, so here is a fix-up I think is more correct.
According to the error log in the original post [2], the build failed
in scripts/mod/devicetable-offsets.c
scripts/mod/Makefile is descended from scripts/Makefile, which is
invoked from the top-level Makefile by the 'scripts' target.
To build vmlinux and/or modules, Kbuild descend into $(vmlinux-dirs).
This depends on 'prepare' and 'scripts' as follows:
$(vmlinux-dirs): prepare scripts
Because there is no dependency between 'prepare' and 'scripts', the
parallel building can execute them simultaneously.
'prepare' depends on 'prepare1', which touched autoksyms.h, while
'scripts' descends into script/, then scripts/mod/, which needs
<generated/autoksyms.h> if CONFIG_TRIM_UNUSED_KSYMS. It was the
reason of the race.
I am not happy to have unrelated code in the Kconfig Makefile, so
getting it back to the top Makefile.
I removed the standalone test target because I want to use it to
create an empty autoksyms.h file. Here is a little improvement;
unnecessary autoksyms.h is not created when CONFIG_TRIM_UNUSED_KSYMS
is disabled.
[1] https://lkml.org/lkml/2016/11/30/734
[2] https://lkml.org/lkml/2016/11/30/531
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Nicolas Pitre <nico@linaro.org>
2018-03-16 07:37:12 +00:00
|
|
|
$(autoksyms_h):
|
2020-02-28 17:20:15 +00:00
|
|
|
$(call cmd,autoksyms_h)
|
2016-01-27 02:50:18 +00:00
|
|
|
|
2016-08-24 12:29:21 +00:00
|
|
|
ARCH_POSTLINK := $(wildcard $(srctree)/arch/$(SRCARCH)/Makefile.postlink)
|
|
|
|
|
|
|
|
|
|
# Final link of vmlinux with optional arch pass after final link
|
2017-08-02 02:31:06 +00:00
|
|
|
cmd_link-vmlinux = \
|
2018-08-23 23:20:39 +00:00
|
|
|
$(CONFIG_SHELL) $< $(LD) $(KBUILD_LDFLAGS) $(LDFLAGS_vmlinux) ; \
|
2016-08-24 12:29:21 +00:00
|
|
|
$(if $(ARCH_POSTLINK), $(MAKE) -f $(ARCH_POSTLINK) $@, true)
|
2016-04-22 19:25:00 +00:00
|
|
|
|
2018-03-16 07:37:15 +00:00
|
|
|
vmlinux: scripts/link-vmlinux.sh autoksyms_recursive $(vmlinux-deps) FORCE
|
2012-05-05 08:18:41 +00:00
|
|
|
+$(call if_changed,link-vmlinux)
|
2007-07-17 08:54:06 +00:00
|
|
|
|
kbuild: let fixdep directly write to .*.cmd files
Currently, fixdep writes dependencies to .*.tmp, which is renamed to
.*.cmd after everything succeeds. This is a very safe way to avoid
corrupted .*.cmd files. The if_changed_dep has carried this safety
mechanism since it was added in 2002.
If fixdep fails for some reasons or a user terminates the build while
fixdep is running, the incomplete output from the fixdep could be
troublesome.
This is my insight about some bad scenarios:
[1] If the compiler succeeds to generate *.o file, but fixdep fails
to write necessary dependencies to .*.cmd file, Make will miss
to rebuild the object when headers or CONFIG options are changed.
In this case, fixdep should not generate .*.cmd file at all so
that 'arg-check' will surely trigger the rebuild of the object.
[2] A partially constructed .*.cmd file may not be a syntactically
correct makefile. The next time Make runs, it would include it,
then fail to parse it. Once this happens, 'make clean' is be the
only way to fix it.
In fact, [1] is no longer a problem since commit 9c2af1c7377a ("kbuild:
add .DELETE_ON_ERROR special target"). Make deletes a target file on
any failure in its recipe. Because fixdep is a part of the recipe of
*.o target, if it fails, the *.o is deleted anyway. However, I am a
bit worried about the slight possibility of [2].
So, here is a solution. Let fixdep directly write to a .*.cmd file,
but allow makefiles to include it only when its corresponding target
exists.
This effectively reverts commit 2982c953570b ("kbuild: remove redundant
$(wildcard ...) for cmd_files calculation"), and commit 00d78ab2ba75
("kbuild: remove dead code in cmd_files calculation in top Makefile")
because now we must check the presence of targets.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2018-11-30 01:05:22 +00:00
|
|
|
targets := vmlinux
|
|
|
|
|
|
2014-04-28 07:26:18 +00:00
|
|
|
# The actual objects are generated when descending,
|
2005-04-16 22:20:36 +00:00
|
|
|
# make sure no implicit rule kicks in
|
2020-06-01 05:57:00 +00:00
|
|
|
$(sort $(vmlinux-deps) $(subdir-modorder)): descend ;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-01-03 01:16:54 +00:00
|
|
|
filechk_kernel.release = \
|
2013-07-11 13:34:51 +00:00
|
|
|
echo "$(KERNELVERSION)$$($(CONFIG_SHELL) $(srctree)/scripts/setlocalversion $(srctree))"
|
|
|
|
|
|
2013-06-28 09:27:31 +00:00
|
|
|
# Store (new) KERNELRELEASE string in include/config/kernel.release
|
2019-04-07 10:03:18 +00:00
|
|
|
include/config/kernel.release: FORCE
|
2013-07-11 13:34:51 +00:00
|
|
|
$(call filechk,kernel.release)
|
2006-01-09 20:20:34 +00:00
|
|
|
|
2018-03-16 07:37:11 +00:00
|
|
|
# Additional helpers built in scripts/
|
|
|
|
|
# Carefully list dependencies so we do not try to build scripts twice
|
|
|
|
|
# in parallel
|
|
|
|
|
PHONY += scripts
|
2018-11-29 03:13:24 +00:00
|
|
|
scripts: scripts_basic scripts_dtc
|
2018-03-16 07:37:11 +00:00
|
|
|
$(Q)$(MAKE) $(build)=$(@)
|
2006-01-09 20:20:34 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# Things we need to do before we recursively start building the kernel
|
2005-09-11 20:30:22 +00:00
|
|
|
# or the modules are listed in "prepare".
|
|
|
|
|
# A multi level approach is used. prepareN is processed before prepareN-1.
|
|
|
|
|
# archprepare is used in arch Makefiles and when processed asm symlink,
|
|
|
|
|
# version.h and scripts_basic is processed / created.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-08-22 04:46:12 +00:00
|
|
|
PHONY += prepare archprepare
|
2005-09-11 20:30:22 +00:00
|
|
|
|
2019-08-22 04:46:13 +00:00
|
|
|
archprepare: outputmakefile archheaders archscripts scripts include/config/kernel.release \
|
2020-05-01 06:01:41 +00:00
|
|
|
asm-generic $(version_h) $(autoksyms_h) include/generated/utsrelease.h \
|
|
|
|
|
include/generated/autoconf.h
|
2005-09-11 20:30:22 +00:00
|
|
|
|
2018-11-29 02:58:50 +00:00
|
|
|
prepare0: archprepare
|
2018-11-29 03:13:24 +00:00
|
|
|
$(Q)$(MAKE) $(build)=scripts/mod
|
2005-09-10 19:05:36 +00:00
|
|
|
$(Q)$(MAKE) $(build)=.
|
2005-09-09 17:28:28 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# All the preparing..
|
2016-02-29 04:22:42 +00:00
|
|
|
prepare: prepare0 prepare-objtool
|
|
|
|
|
|
2017-10-04 03:56:06 +00:00
|
|
|
# Support for using generic headers in asm-generic
|
2018-12-05 11:28:04 +00:00
|
|
|
asm-generic := -f $(srctree)/scripts/Makefile.asm-generic obj
|
|
|
|
|
|
2017-10-04 03:56:06 +00:00
|
|
|
PHONY += asm-generic uapi-asm-generic
|
|
|
|
|
asm-generic: uapi-asm-generic
|
2019-03-17 02:01:09 +00:00
|
|
|
$(Q)$(MAKE) $(asm-generic)=arch/$(SRCARCH)/include/generated/asm \
|
|
|
|
|
generic=include/asm-generic
|
2017-10-04 03:56:06 +00:00
|
|
|
uapi-asm-generic:
|
2019-03-17 02:01:09 +00:00
|
|
|
$(Q)$(MAKE) $(asm-generic)=arch/$(SRCARCH)/include/generated/uapi/asm \
|
|
|
|
|
generic=include/uapi/asm-generic
|
2017-10-04 03:56:06 +00:00
|
|
|
|
2016-02-29 04:22:42 +00:00
|
|
|
PHONY += prepare-objtool
|
2016-03-03 17:39:30 +00:00
|
|
|
prepare-objtool: $(objtool_target)
|
2018-12-18 05:25:41 +00:00
|
|
|
ifeq ($(SKIP_STACK_VALIDATION),1)
|
|
|
|
|
ifdef CONFIG_UNWINDER_ORC
|
|
|
|
|
@echo "error: Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel" >&2
|
|
|
|
|
@false
|
|
|
|
|
else
|
|
|
|
|
@echo "warning: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel" >&2
|
|
|
|
|
endif
|
|
|
|
|
endif
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# Generate some files
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
# KERNELRELEASE can change from a few different places, meaning version.h
|
|
|
|
|
# needs to be updated, so this check is forced on all builds
|
|
|
|
|
|
|
|
|
|
uts_len := 64
|
2006-07-03 21:30:54 +00:00
|
|
|
define filechk_utsrelease.h
|
|
|
|
|
if [ `echo -n "$(KERNELRELEASE)" | wc -c ` -gt $(uts_len) ]; then \
|
|
|
|
|
echo '"$(KERNELRELEASE)" exceeds $(uts_len) characters' >&2; \
|
|
|
|
|
exit 1; \
|
|
|
|
|
fi; \
|
2018-12-31 08:24:09 +00:00
|
|
|
echo \#define UTS_RELEASE \"$(KERNELRELEASE)\"
|
2006-07-03 21:30:54 +00:00
|
|
|
endef
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
define filechk_version.h
|
2018-12-31 08:24:09 +00:00
|
|
|
echo \#define LINUX_VERSION_CODE $(shell \
|
2012-02-16 21:49:15 +00:00
|
|
|
expr $(VERSION) \* 65536 + 0$(PATCHLEVEL) \* 256 + 0$(SUBLEVEL)); \
|
2018-12-31 08:24:09 +00:00
|
|
|
echo '#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))'
|
2005-04-16 22:20:36 +00:00
|
|
|
endef
|
|
|
|
|
|
2018-07-25 05:16:11 +00:00
|
|
|
$(version_h): FORCE
|
2005-04-16 22:20:36 +00:00
|
|
|
$(call filechk,version.h)
|
2014-11-27 15:13:17 +00:00
|
|
|
$(Q)rm -f $(old_version_h)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2009-10-17 22:52:28 +00:00
|
|
|
include/generated/utsrelease.h: include/config/kernel.release FORCE
|
2006-07-03 21:30:54 +00:00
|
|
|
$(call filechk,utsrelease.h)
|
|
|
|
|
|
2008-12-16 11:33:43 +00:00
|
|
|
PHONY += headerdep
|
|
|
|
|
headerdep:
|
2011-04-26 21:17:11 +00:00
|
|
|
$(Q)find $(srctree)/include/ -name '*.h' | xargs --max-args 1 \
|
|
|
|
|
$(srctree)/scripts/headerdep.pl -I$(srctree)/include
|
2008-12-16 11:33:43 +00:00
|
|
|
|
2006-06-18 10:58:39 +00:00
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
# Kernel headers
|
|
|
|
|
|
2008-06-05 14:43:46 +00:00
|
|
|
#Default location for installed headers
|
|
|
|
|
export INSTALL_HDR_PATH = $(objtree)/usr
|
2006-09-24 21:16:03 +00:00
|
|
|
|
kbuild: add 'headers' target to build up uapi headers in usr/include
In Linux build system, build targets and installation targets are
separated.
Examples are:
- 'make vmlinux' -> 'make install'
- 'make modules' -> 'make modules_install'
- 'make dtbs' -> 'make dtbs_install'
- 'make vdso' -> 'make vdso_install'
The intention is to run the build targets under the normal privilege,
then the installation targets under the root privilege since we need
the write permission to the system directories.
We have 'make headers_install' but the corresponding 'make headers'
stage does not exist. The purpose of headers_install is to provide
the kernel interface to C library. So, nobody would try to install
headers to /usr/include directly.
If 'sudo make INSTALL_HDR_PATH=/usr/include headers_install' were run,
some build artifacts in the kernel tree would be owned by root because
some of uapi headers are generated by 'uapi-asm-generic', 'archheaders'
targets.
Anyway, I believe it makes sense to split the header installation into
two stages.
[1] 'make headers'
Process headers in uapi directories by scripts/headers_install.sh
and copy them to usr/include
[2] 'make headers_install'
Copy '*.h' verbatim from usr/include to $(INSTALL_HDR_PATH)/include
For the backward compatibility, 'headers_install' depends on 'headers'.
Some samples expect uapi headers in usr/include. So, the 'headers'
target is useful to build up them in the fixed location usr/include
irrespective of INSTALL_HDR_PATH.
Another benefit is to stop polluting the final destination with the
time-stamp files '.install' and '.check'. Maybe you can see them in
your toolchains.
Lastly, my main motivation is to prepare for compile-testing uapi
headers. To build something, we have to save an object and .*.cmd
somewhere. The usr/include/ will be the work directory for that.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-06-04 10:14:02 +00:00
|
|
|
quiet_cmd_headers_install = INSTALL $(INSTALL_HDR_PATH)/include
|
|
|
|
|
cmd_headers_install = \
|
|
|
|
|
mkdir -p $(INSTALL_HDR_PATH); \
|
|
|
|
|
rsync -mrl --include='*/' --include='*\.h' --exclude='*' \
|
|
|
|
|
usr/include $(INSTALL_HDR_PATH)
|
2008-06-05 14:43:46 +00:00
|
|
|
|
2006-06-18 10:58:39 +00:00
|
|
|
PHONY += headers_install
|
kbuild: add 'headers' target to build up uapi headers in usr/include
In Linux build system, build targets and installation targets are
separated.
Examples are:
- 'make vmlinux' -> 'make install'
- 'make modules' -> 'make modules_install'
- 'make dtbs' -> 'make dtbs_install'
- 'make vdso' -> 'make vdso_install'
The intention is to run the build targets under the normal privilege,
then the installation targets under the root privilege since we need
the write permission to the system directories.
We have 'make headers_install' but the corresponding 'make headers'
stage does not exist. The purpose of headers_install is to provide
the kernel interface to C library. So, nobody would try to install
headers to /usr/include directly.
If 'sudo make INSTALL_HDR_PATH=/usr/include headers_install' were run,
some build artifacts in the kernel tree would be owned by root because
some of uapi headers are generated by 'uapi-asm-generic', 'archheaders'
targets.
Anyway, I believe it makes sense to split the header installation into
two stages.
[1] 'make headers'
Process headers in uapi directories by scripts/headers_install.sh
and copy them to usr/include
[2] 'make headers_install'
Copy '*.h' verbatim from usr/include to $(INSTALL_HDR_PATH)/include
For the backward compatibility, 'headers_install' depends on 'headers'.
Some samples expect uapi headers in usr/include. So, the 'headers'
target is useful to build up them in the fixed location usr/include
irrespective of INSTALL_HDR_PATH.
Another benefit is to stop polluting the final destination with the
time-stamp files '.install' and '.check'. Maybe you can see them in
your toolchains.
Lastly, my main motivation is to prepare for compile-testing uapi
headers. To build something, we have to save an object and .*.cmd
somewhere. The usr/include/ will be the work directory for that.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-06-04 10:14:02 +00:00
|
|
|
headers_install: headers
|
|
|
|
|
$(call cmd,headers_install)
|
2012-05-08 18:22:24 +00:00
|
|
|
|
kbuild: add 'headers' target to build up uapi headers in usr/include
In Linux build system, build targets and installation targets are
separated.
Examples are:
- 'make vmlinux' -> 'make install'
- 'make modules' -> 'make modules_install'
- 'make dtbs' -> 'make dtbs_install'
- 'make vdso' -> 'make vdso_install'
The intention is to run the build targets under the normal privilege,
then the installation targets under the root privilege since we need
the write permission to the system directories.
We have 'make headers_install' but the corresponding 'make headers'
stage does not exist. The purpose of headers_install is to provide
the kernel interface to C library. So, nobody would try to install
headers to /usr/include directly.
If 'sudo make INSTALL_HDR_PATH=/usr/include headers_install' were run,
some build artifacts in the kernel tree would be owned by root because
some of uapi headers are generated by 'uapi-asm-generic', 'archheaders'
targets.
Anyway, I believe it makes sense to split the header installation into
two stages.
[1] 'make headers'
Process headers in uapi directories by scripts/headers_install.sh
and copy them to usr/include
[2] 'make headers_install'
Copy '*.h' verbatim from usr/include to $(INSTALL_HDR_PATH)/include
For the backward compatibility, 'headers_install' depends on 'headers'.
Some samples expect uapi headers in usr/include. So, the 'headers'
target is useful to build up them in the fixed location usr/include
irrespective of INSTALL_HDR_PATH.
Another benefit is to stop polluting the final destination with the
time-stamp files '.install' and '.check'. Maybe you can see them in
your toolchains.
Lastly, my main motivation is to prepare for compile-testing uapi
headers. To build something, we have to save an object and .*.cmd
somewhere. The usr/include/ will be the work directory for that.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-06-04 10:14:02 +00:00
|
|
|
PHONY += archheaders archscripts
|
2008-06-05 14:43:46 +00:00
|
|
|
|
2019-06-04 10:14:04 +00:00
|
|
|
hdr-inst := -f $(srctree)/scripts/Makefile.headersinst obj
|
2006-09-24 21:16:03 +00:00
|
|
|
|
kbuild: add 'headers' target to build up uapi headers in usr/include
In Linux build system, build targets and installation targets are
separated.
Examples are:
- 'make vmlinux' -> 'make install'
- 'make modules' -> 'make modules_install'
- 'make dtbs' -> 'make dtbs_install'
- 'make vdso' -> 'make vdso_install'
The intention is to run the build targets under the normal privilege,
then the installation targets under the root privilege since we need
the write permission to the system directories.
We have 'make headers_install' but the corresponding 'make headers'
stage does not exist. The purpose of headers_install is to provide
the kernel interface to C library. So, nobody would try to install
headers to /usr/include directly.
If 'sudo make INSTALL_HDR_PATH=/usr/include headers_install' were run,
some build artifacts in the kernel tree would be owned by root because
some of uapi headers are generated by 'uapi-asm-generic', 'archheaders'
targets.
Anyway, I believe it makes sense to split the header installation into
two stages.
[1] 'make headers'
Process headers in uapi directories by scripts/headers_install.sh
and copy them to usr/include
[2] 'make headers_install'
Copy '*.h' verbatim from usr/include to $(INSTALL_HDR_PATH)/include
For the backward compatibility, 'headers_install' depends on 'headers'.
Some samples expect uapi headers in usr/include. So, the 'headers'
target is useful to build up them in the fixed location usr/include
irrespective of INSTALL_HDR_PATH.
Another benefit is to stop polluting the final destination with the
time-stamp files '.install' and '.check'. Maybe you can see them in
your toolchains.
Lastly, my main motivation is to prepare for compile-testing uapi
headers. To build something, we have to save an object and .*.cmd
somewhere. The usr/include/ will be the work directory for that.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-06-04 10:14:02 +00:00
|
|
|
PHONY += headers
|
|
|
|
|
headers: $(version_h) scripts_unifdef uapi-asm-generic archheaders archscripts
|
2017-10-04 03:56:04 +00:00
|
|
|
$(if $(wildcard $(srctree)/arch/$(SRCARCH)/include/uapi/asm/Kbuild),, \
|
2012-10-02 17:01:57 +00:00
|
|
|
$(error Headers not exportable for the $(SRCARCH) architecture))
|
2019-06-04 10:14:03 +00:00
|
|
|
$(Q)$(MAKE) $(hdr-inst)=include/uapi
|
|
|
|
|
$(Q)$(MAKE) $(hdr-inst)=arch/$(SRCARCH)/include/uapi
|
2007-02-14 08:33:02 +00:00
|
|
|
|
2019-11-07 07:14:41 +00:00
|
|
|
# Deprecated. It is no-op now.
|
2006-06-18 11:02:10 +00:00
|
|
|
PHONY += headers_check
|
2019-11-07 07:14:41 +00:00
|
|
|
headers_check:
|
|
|
|
|
@:
|
2006-06-18 11:02:10 +00:00
|
|
|
|
2019-06-04 10:13:59 +00:00
|
|
|
ifdef CONFIG_HEADERS_INSTALL
|
kbuild: add 'headers' target to build up uapi headers in usr/include
In Linux build system, build targets and installation targets are
separated.
Examples are:
- 'make vmlinux' -> 'make install'
- 'make modules' -> 'make modules_install'
- 'make dtbs' -> 'make dtbs_install'
- 'make vdso' -> 'make vdso_install'
The intention is to run the build targets under the normal privilege,
then the installation targets under the root privilege since we need
the write permission to the system directories.
We have 'make headers_install' but the corresponding 'make headers'
stage does not exist. The purpose of headers_install is to provide
the kernel interface to C library. So, nobody would try to install
headers to /usr/include directly.
If 'sudo make INSTALL_HDR_PATH=/usr/include headers_install' were run,
some build artifacts in the kernel tree would be owned by root because
some of uapi headers are generated by 'uapi-asm-generic', 'archheaders'
targets.
Anyway, I believe it makes sense to split the header installation into
two stages.
[1] 'make headers'
Process headers in uapi directories by scripts/headers_install.sh
and copy them to usr/include
[2] 'make headers_install'
Copy '*.h' verbatim from usr/include to $(INSTALL_HDR_PATH)/include
For the backward compatibility, 'headers_install' depends on 'headers'.
Some samples expect uapi headers in usr/include. So, the 'headers'
target is useful to build up them in the fixed location usr/include
irrespective of INSTALL_HDR_PATH.
Another benefit is to stop polluting the final destination with the
time-stamp files '.install' and '.check'. Maybe you can see them in
your toolchains.
Lastly, my main motivation is to prepare for compile-testing uapi
headers. To build something, we have to save an object and .*.cmd
somewhere. The usr/include/ will be the work directory for that.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2019-06-04 10:14:02 +00:00
|
|
|
prepare: headers
|
2019-06-04 10:13:59 +00:00
|
|
|
endif
|
2006-06-18 11:02:10 +00:00
|
|
|
|
2019-06-04 10:14:01 +00:00
|
|
|
PHONY += scripts_unifdef
|
|
|
|
|
scripts_unifdef: scripts_basic
|
|
|
|
|
$(Q)$(MAKE) $(build)=scripts scripts/unifdef
|
|
|
|
|
|
2014-08-07 19:07:46 +00:00
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
# Kernel selftest
|
|
|
|
|
|
|
|
|
|
PHONY += kselftest
|
|
|
|
|
kselftest:
|
2017-09-06 22:44:35 +00:00
|
|
|
$(Q)$(MAKE) -C $(srctree)/tools/testing/selftests run_tests
|
2014-08-07 19:07:46 +00:00
|
|
|
|
2019-09-26 22:40:14 +00:00
|
|
|
kselftest-%: FORCE
|
|
|
|
|
$(Q)$(MAKE) -C $(srctree)/tools/testing/selftests $*
|
2015-10-08 02:41:18 +00:00
|
|
|
|
2016-01-08 07:27:34 +00:00
|
|
|
PHONY += kselftest-merge
|
|
|
|
|
kselftest-merge:
|
|
|
|
|
$(if $(wildcard $(objtree)/.config),, $(error No .config exists, config your kernel first!))
|
2019-05-20 15:16:14 +00:00
|
|
|
$(Q)find $(srctree)/tools/testing/selftests -name config | \
|
|
|
|
|
xargs $(srctree)/scripts/kconfig/merge_config.sh -m $(objtree)/.config
|
2019-08-21 07:03:48 +00:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/Makefile olddefconfig
|
2016-01-08 07:27:34 +00:00
|
|
|
|
2018-01-10 21:19:37 +00:00
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
# Devicetree files
|
|
|
|
|
|
|
|
|
|
ifneq ($(wildcard $(srctree)/arch/$(SRCARCH)/boot/dts/),)
|
|
|
|
|
dtstree := arch/$(SRCARCH)/boot/dts
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
ifneq ($(dtstree),)
|
|
|
|
|
|
2019-08-22 04:46:12 +00:00
|
|
|
%.dtb: include/config/kernel.release scripts_dtc
|
2018-01-10 21:19:37 +00:00
|
|
|
$(Q)$(MAKE) $(build)=$(dtstree) $(dtstree)/$@
|
|
|
|
|
|
2020-02-22 19:04:34 +00:00
|
|
|
PHONY += dtbs dtbs_install dtbs_check
|
2020-03-04 03:20:36 +00:00
|
|
|
dtbs: include/config/kernel.release scripts_dtc
|
2018-01-10 21:19:37 +00:00
|
|
|
$(Q)$(MAKE) $(build)=$(dtstree)
|
|
|
|
|
|
2020-03-04 03:20:36 +00:00
|
|
|
ifneq ($(filter dtbs_check, $(MAKECMDGOALS)),)
|
2020-03-04 03:20:37 +00:00
|
|
|
export CHECK_DTBS=y
|
2020-03-04 03:20:36 +00:00
|
|
|
dtbs: dt_binding_check
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
dtbs_check: dtbs
|
2018-09-06 18:26:07 +00:00
|
|
|
|
2018-01-10 21:19:37 +00:00
|
|
|
dtbs_install:
|
2020-03-06 17:08:51 +00:00
|
|
|
$(Q)$(MAKE) $(dtbinst)=$(dtstree) dst=$(INSTALL_DTBS_PATH)
|
2018-01-10 21:19:37 +00:00
|
|
|
|
|
|
|
|
ifdef CONFIG_OF_EARLY_FLATTREE
|
|
|
|
|
all: dtbs
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
PHONY += scripts_dtc
|
|
|
|
|
scripts_dtc: scripts_basic
|
|
|
|
|
$(Q)$(MAKE) $(build)=scripts/dtc
|
|
|
|
|
|
2020-03-04 03:20:37 +00:00
|
|
|
ifneq ($(filter dt_binding_check, $(MAKECMDGOALS)),)
|
|
|
|
|
export CHECK_DT_BINDING=y
|
|
|
|
|
endif
|
|
|
|
|
|
2020-02-22 19:04:34 +00:00
|
|
|
PHONY += dt_binding_check
|
2018-09-06 18:26:07 +00:00
|
|
|
dt_binding_check: scripts_dtc
|
|
|
|
|
$(Q)$(MAKE) $(build)=Documentation/devicetree/bindings
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
# Modules
|
|
|
|
|
|
|
|
|
|
ifdef CONFIG_MODULES
|
|
|
|
|
|
2006-06-24 22:07:55 +00:00
|
|
|
# By default, build modules as well
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2010-03-10 11:28:58 +00:00
|
|
|
all: modules
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-05-31 08:47:06 +00:00
|
|
|
# When we're building modules with modversions, we need to consider
|
|
|
|
|
# the built-in objects during the descend as well, in order to
|
|
|
|
|
# make sure the checksums are up to date before we record them.
|
|
|
|
|
ifdef CONFIG_MODVERSIONS
|
|
|
|
|
KBUILD_BUILTIN := 1
|
|
|
|
|
endif
|
|
|
|
|
|
2014-04-28 07:32:43 +00:00
|
|
|
# Build modules
|
2007-12-07 12:04:30 +00:00
|
|
|
#
|
2014-04-28 07:32:43 +00:00
|
|
|
# A module can be listed more than once in obj-m resulting in
|
|
|
|
|
# duplicate lines in modules.order files. Those are removed
|
|
|
|
|
# using awk while concatenating to the final file.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += modules
|
2020-05-11 04:21:49 +00:00
|
|
|
modules: $(if $(KBUILD_BUILTIN),vmlinux) modules_check
|
2006-08-08 19:36:08 +00:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-05-11 04:21:49 +00:00
|
|
|
PHONY += modules_check
|
|
|
|
|
modules_check: modules.order
|
|
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/modules-check.sh $<
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-06-01 05:57:00 +00:00
|
|
|
cmd_modules_order = $(AWK) '!x[$$0]++' $(real-prereqs) > $@
|
|
|
|
|
|
|
|
|
|
modules.order: $(subdir-modorder) FORCE
|
|
|
|
|
$(call if_changed,modules_order)
|
|
|
|
|
|
|
|
|
|
targets += modules.order
|
2019-06-23 16:13:28 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# Target to prepare building external modules
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += modules_prepare
|
2018-11-29 03:56:30 +00:00
|
|
|
modules_prepare: prepare
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# Target to install modules
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += modules_install
|
2005-04-16 22:20:36 +00:00
|
|
|
modules_install: _modinst_ _modinst_post
|
|
|
|
|
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += _modinst_
|
2020-06-19 15:09:55 +00:00
|
|
|
_modinst_:
|
2005-04-16 22:20:36 +00:00
|
|
|
@rm -rf $(MODLIB)/kernel
|
|
|
|
|
@rm -f $(MODLIB)/source
|
|
|
|
|
@mkdir -p $(MODLIB)/kernel
|
2017-08-20 06:04:11 +00:00
|
|
|
@ln -s $(abspath $(srctree)) $(MODLIB)/source
|
2005-04-16 22:20:36 +00:00
|
|
|
@if [ ! $(objtree) -ef $(MODLIB)/build ]; then \
|
|
|
|
|
rm -f $(MODLIB)/build ; \
|
2014-04-25 15:29:45 +00:00
|
|
|
ln -s $(CURDIR) $(MODLIB)/build ; \
|
2005-04-16 22:20:36 +00:00
|
|
|
fi
|
2019-07-17 06:17:50 +00:00
|
|
|
@sed 's:^:kernel/:' modules.order > $(MODLIB)/modules.order
|
2020-06-19 15:09:55 +00:00
|
|
|
@cp -f modules.builtin $(MODLIB)/
|
|
|
|
|
@cp -f $(objtree)/modules.builtin.modinfo $(MODLIB)/
|
2006-08-08 19:36:08 +00:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modinst
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-10-18 19:24:21 +00:00
|
|
|
# This depmod is only for convenience to give the initial
|
2005-04-16 22:20:36 +00:00
|
|
|
# boot a modules.dep even before / is mounted read-write. However the
|
|
|
|
|
# boot script depmod is the master version.
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += _modinst_post
|
2013-07-11 02:02:51 +00:00
|
|
|
_modinst_post: _modinst_
|
2007-10-18 19:24:21 +00:00
|
|
|
$(call cmd,depmod)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2012-11-04 22:39:24 +00:00
|
|
|
ifeq ($(CONFIG_MODULE_SIG), y)
|
|
|
|
|
PHONY += modules_sign
|
|
|
|
|
modules_sign:
|
|
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modsign
|
|
|
|
|
endif
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
else # CONFIG_MODULES
|
|
|
|
|
|
|
|
|
|
# Modules not configured
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
2016-03-13 00:39:22 +00:00
|
|
|
PHONY += modules modules_install
|
|
|
|
|
modules modules_install:
|
2012-07-07 21:04:40 +00:00
|
|
|
@echo >&2
|
|
|
|
|
@echo >&2 "The present kernel configuration has modules disabled."
|
|
|
|
|
@echo >&2 "Type 'make config' and enable loadable module support."
|
|
|
|
|
@echo >&2 "Then build a kernel with module support enabled."
|
|
|
|
|
@echo >&2
|
2005-04-16 22:20:36 +00:00
|
|
|
@exit 1
|
|
|
|
|
|
|
|
|
|
endif # CONFIG_MODULES
|
|
|
|
|
|
|
|
|
|
###
|
|
|
|
|
# Cleaning is done on three levels.
|
|
|
|
|
# make clean Delete most generated files
|
|
|
|
|
# Leave enough to build external modules
|
|
|
|
|
# make mrproper Delete the current configuration, and all generated files
|
|
|
|
|
# make distclean Remove editor backup files, patch leftover files and the like
|
|
|
|
|
|
|
|
|
|
# Directories & files removed with 'make clean'
|
modpost: generate vmlinux.symvers and reuse it for the second modpost
The full build runs modpost twice, first for vmlinux.o and second for
modules.
The first pass dumps all the vmlinux symbols into Module.symvers, but
the second pass parses vmlinux again instead of reusing the dump file,
presumably because it needs to avoid accumulating stale symbols.
Loading symbol info from a dump file is faster than parsing an ELF object.
Besides, modpost deals with various issues to parse vmlinux in the second
pass.
A solution is to make the first pass dumps symbols into a separate file,
vmlinux.symvers. The second pass reads it, and parses module .o files.
The merged symbol information is dumped into Module.symvers in the same
way as before.
This makes further modpost cleanups possible.
Also, it fixes the problem of 'make vmlinux', which previously overwrote
Module.symvers, throwing away module symbols.
I slightly touched scripts/link-vmlinux.sh so that vmlinux is re-linked
when you cross this commit. Otherwise, vmlinux.symvers would not be
generated.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2020-06-01 05:57:11 +00:00
|
|
|
CLEAN_FILES += include/ksym vmlinux.symvers \
|
2020-05-04 08:08:07 +00:00
|
|
|
modules.builtin modules.builtin.modinfo modules.nsdeps
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# Directories & files removed with 'make mrproper'
|
2020-05-04 08:08:07 +00:00
|
|
|
MRPROPER_FILES += include/config include/generated \
|
2019-08-21 07:02:02 +00:00
|
|
|
arch/$(SRCARCH)/include/generated .tmp_objdiff \
|
2020-05-04 08:08:07 +00:00
|
|
|
debian snap tar-install \
|
|
|
|
|
.config .config.old .version \
|
2019-07-15 14:01:49 +00:00
|
|
|
Module.symvers \
|
2015-07-20 20:16:30 +00:00
|
|
|
signing_key.pem signing_key.priv signing_key.x509 \
|
|
|
|
|
x509.genkey extra_certificates signing_key.x509.keyid \
|
2019-08-21 07:02:02 +00:00
|
|
|
signing_key.x509.signer vmlinux-gdb.py \
|
|
|
|
|
*.spec
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-07-15 14:01:49 +00:00
|
|
|
# Directories & files removed with 'make distclean'
|
|
|
|
|
DISTCLEAN_FILES += tags TAGS cscope* GPATH GTAGS GRTAGS GSYMS
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# clean - Delete most, but leave enough to build external modules
|
|
|
|
|
#
|
|
|
|
|
clean: rm-files := $(CLEAN_FILES)
|
|
|
|
|
|
2019-08-10 15:53:05 +00:00
|
|
|
PHONY += archclean vmlinuxclean
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2012-10-29 11:23:02 +00:00
|
|
|
vmlinuxclean:
|
|
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/link-vmlinux.sh clean
|
2016-08-24 12:29:21 +00:00
|
|
|
$(Q)$(if $(ARCH_POSTLINK), $(MAKE) -f $(ARCH_POSTLINK) clean)
|
2012-10-29 11:23:02 +00:00
|
|
|
|
|
|
|
|
clean: archclean vmlinuxclean
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# mrproper - Delete all generated files, including .config
|
|
|
|
|
#
|
|
|
|
|
mrproper: rm-files := $(wildcard $(MRPROPER_FILES))
|
2017-05-14 14:50:01 +00:00
|
|
|
mrproper-dirs := $(addprefix _mrproper_,scripts)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-01-14 08:29:29 +00:00
|
|
|
PHONY += $(mrproper-dirs) mrproper
|
2005-04-16 22:20:36 +00:00
|
|
|
$(mrproper-dirs):
|
|
|
|
|
$(Q)$(MAKE) $(clean)=$(patsubst _mrproper_%,%,$@)
|
|
|
|
|
|
2019-01-14 08:29:29 +00:00
|
|
|
mrproper: clean $(mrproper-dirs)
|
2005-04-16 22:20:36 +00:00
|
|
|
$(call cmd,rmfiles)
|
|
|
|
|
|
|
|
|
|
# distclean
|
|
|
|
|
#
|
2019-07-15 14:01:49 +00:00
|
|
|
distclean: rm-files := $(wildcard $(DISTCLEAN_FILES))
|
|
|
|
|
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += distclean
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
distclean: mrproper
|
2019-07-15 14:01:49 +00:00
|
|
|
$(call cmd,rmfiles)
|
2005-04-16 22:20:36 +00:00
|
|
|
@find $(srctree) $(RCS_FIND_IGNORE) \
|
2006-06-24 22:07:55 +00:00
|
|
|
\( -name '*.orig' -o -name '*.rej' -o -name '*~' \
|
2017-01-22 14:02:32 +00:00
|
|
|
-o -name '*.bak' -o -name '#*#' -o -name '*%' \
|
|
|
|
|
-o -name 'core' \) \
|
2005-04-16 22:20:36 +00:00
|
|
|
-type f -print | xargs rm -f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Packaging of the kernel to various formats
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
2010-06-07 10:44:25 +00:00
|
|
|
%src-pkg: FORCE
|
2019-08-21 07:02:04 +00:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.package $@
|
2006-06-09 05:12:37 +00:00
|
|
|
%pkg: include/config/kernel.release FORCE
|
2019-08-21 07:02:04 +00:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.package $@
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
# Brief documentation of the typical targets used
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
2008-04-06 20:16:07 +00:00
|
|
|
boards := $(wildcard $(srctree)/arch/$(SRCARCH)/configs/*_defconfig)
|
2014-10-28 13:18:20 +00:00
|
|
|
boards := $(sort $(notdir $(boards)))
|
2008-04-06 20:16:07 +00:00
|
|
|
board-dirs := $(dir $(wildcard $(srctree)/arch/$(SRCARCH)/configs/*/*_defconfig))
|
|
|
|
|
board-dirs := $(sort $(notdir $(board-dirs:/=)))
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2016-03-13 00:39:55 +00:00
|
|
|
PHONY += help
|
2005-04-16 22:20:36 +00:00
|
|
|
help:
|
|
|
|
|
@echo 'Cleaning targets:'
|
2006-12-12 18:09:40 +00:00
|
|
|
@echo ' clean - Remove most generated files but keep the config and'
|
2006-09-24 12:01:08 +00:00
|
|
|
@echo ' enough build support to build external modules'
|
2006-12-12 18:09:40 +00:00
|
|
|
@echo ' mrproper - Remove all generated files + config + various backup files'
|
2006-09-24 12:01:08 +00:00
|
|
|
@echo ' distclean - mrproper + remove editor backup and patch files'
|
2005-04-16 22:20:36 +00:00
|
|
|
@echo ''
|
|
|
|
|
@echo 'Configuration targets:'
|
|
|
|
|
@$(MAKE) -f $(srctree)/scripts/kconfig/Makefile help
|
|
|
|
|
@echo ''
|
|
|
|
|
@echo 'Other generic targets:'
|
|
|
|
|
@echo ' all - Build all targets marked with [*]'
|
|
|
|
|
@echo '* vmlinux - Build the bare kernel'
|
|
|
|
|
@echo '* modules - Build all modules'
|
2005-11-23 19:11:34 +00:00
|
|
|
@echo ' modules_install - Install all modules to INSTALL_MOD_PATH (default: /)'
|
2005-04-16 22:20:36 +00:00
|
|
|
@echo ' dir/ - Build all files in dir and below'
|
2015-12-10 16:35:19 +00:00
|
|
|
@echo ' dir/file.[ois] - Build specified target only'
|
2017-04-24 20:04:58 +00:00
|
|
|
@echo ' dir/file.ll - Build the LLVM assembly file'
|
|
|
|
|
@echo ' (requires compiler support for LLVM assembly generation)'
|
2010-01-13 17:31:44 +00:00
|
|
|
@echo ' dir/file.lst - Build specified mixed source/assembly target only'
|
|
|
|
|
@echo ' (requires a recent binutils and recent build (System.map))'
|
2005-07-08 00:56:08 +00:00
|
|
|
@echo ' dir/file.ko - Build module including final link'
|
2009-04-24 16:35:23 +00:00
|
|
|
@echo ' modules_prepare - Set up for building external modules'
|
2005-04-16 22:20:36 +00:00
|
|
|
@echo ' tags/TAGS - Generate tags file for editors'
|
|
|
|
|
@echo ' cscope - Generate cscope index'
|
2011-01-14 12:07:05 +00:00
|
|
|
@echo ' gtags - Generate GNU GLOBAL index'
|
2014-07-11 13:57:24 +00:00
|
|
|
@echo ' kernelrelease - Output the release version string (use with make -s)'
|
|
|
|
|
@echo ' kernelversion - Output the version stored in Makefile (use with make -s)'
|
|
|
|
|
@echo ' image_name - Output the image name (use with make -s)'
|
2008-06-20 22:24:17 +00:00
|
|
|
@echo ' headers_install - Install sanitised kernel headers to INSTALL_HDR_PATH'; \
|
2007-01-29 12:47:01 +00:00
|
|
|
echo ' (default: $(INSTALL_HDR_PATH))'; \
|
2008-06-20 22:24:17 +00:00
|
|
|
echo ''
|
2017-05-08 22:55:08 +00:00
|
|
|
@echo 'Static analysers:'
|
2005-04-16 22:20:36 +00:00
|
|
|
@echo ' checkstack - Generate a list of stack hogs'
|
|
|
|
|
@echo ' namespacecheck - Name space analysis on compiled kernel'
|
2007-11-14 20:34:55 +00:00
|
|
|
@echo ' versioncheck - Sanity check on version.h usage'
|
2007-11-04 20:01:55 +00:00
|
|
|
@echo ' includecheck - Check for duplicate included header files'
|
2007-08-24 21:04:56 +00:00
|
|
|
@echo ' export_report - List the usages of all exported symbols'
|
2010-06-06 15:15:01 +00:00
|
|
|
@echo ' headerdep - Detect inclusion cycles in headers'
|
2017-11-14 09:47:20 +00:00
|
|
|
@echo ' coccicheck - Check with Coccinelle'
|
2010-06-06 15:15:01 +00:00
|
|
|
@echo ''
|
2019-09-06 10:32:32 +00:00
|
|
|
@echo 'Tools:'
|
|
|
|
|
@echo ' nsdeps - Generate missing symbol namespace dependencies'
|
|
|
|
|
@echo ''
|
2017-05-08 22:55:08 +00:00
|
|
|
@echo 'Kernel selftest:'
|
2020-03-30 18:07:11 +00:00
|
|
|
@echo ' kselftest - Build and run kernel selftest'
|
|
|
|
|
@echo ' Build, install, and boot kernel before'
|
|
|
|
|
@echo ' running kselftest on it'
|
|
|
|
|
@echo ' Run as root for full coverage'
|
|
|
|
|
@echo ' kselftest-all - Build kernel selftest'
|
|
|
|
|
@echo ' kselftest-install - Build and install kernel selftest'
|
|
|
|
|
@echo ' kselftest-clean - Remove all generated kselftest files'
|
|
|
|
|
@echo ' kselftest-merge - Merge all the config dependencies of'
|
|
|
|
|
@echo ' kselftest to existing .config.'
|
2014-08-07 19:07:46 +00:00
|
|
|
@echo ''
|
2018-01-10 21:19:37 +00:00
|
|
|
@$(if $(dtstree), \
|
|
|
|
|
echo 'Devicetree:'; \
|
2019-08-13 18:38:25 +00:00
|
|
|
echo '* dtbs - Build device tree blobs for enabled boards'; \
|
|
|
|
|
echo ' dtbs_install - Install dtbs to $(INSTALL_DTBS_PATH)'; \
|
|
|
|
|
echo ' dt_binding_check - Validate device tree binding documents'; \
|
|
|
|
|
echo ' dtbs_check - Validate device tree source files';\
|
2018-01-10 21:19:37 +00:00
|
|
|
echo '')
|
|
|
|
|
|
2017-05-08 22:55:08 +00:00
|
|
|
@echo 'Userspace tools targets:'
|
|
|
|
|
@echo ' use "make tools/help"'
|
|
|
|
|
@echo ' or "cd tools; make help"'
|
|
|
|
|
@echo ''
|
2005-04-16 22:20:36 +00:00
|
|
|
@echo 'Kernel packaging:'
|
2019-08-21 07:02:04 +00:00
|
|
|
@$(MAKE) -f $(srctree)/scripts/Makefile.package help
|
2005-04-16 22:20:36 +00:00
|
|
|
@echo ''
|
|
|
|
|
@echo 'Documentation targets:'
|
2017-05-14 14:50:01 +00:00
|
|
|
@$(MAKE) -f $(srctree)/Documentation/Makefile dochelp
|
2005-04-16 22:20:36 +00:00
|
|
|
@echo ''
|
2008-04-26 02:34:58 +00:00
|
|
|
@echo 'Architecture specific targets ($(SRCARCH)):'
|
2005-04-16 22:20:36 +00:00
|
|
|
@$(if $(archhelp),$(archhelp),\
|
2008-04-26 02:34:58 +00:00
|
|
|
echo ' No architecture specific help defined for $(SRCARCH)')
|
2005-04-16 22:20:36 +00:00
|
|
|
@echo ''
|
|
|
|
|
@$(if $(boards), \
|
|
|
|
|
$(foreach b, $(boards), \
|
2019-10-25 11:53:05 +00:00
|
|
|
printf " %-27s - Build for %s\\n" $(b) $(subst _defconfig,,$(b));) \
|
2005-04-16 22:20:36 +00:00
|
|
|
echo '')
|
2008-04-06 20:16:07 +00:00
|
|
|
@$(if $(board-dirs), \
|
|
|
|
|
$(foreach b, $(board-dirs), \
|
|
|
|
|
printf " %-16s - Show %s-specific targets\\n" help-$(b) $(b);) \
|
|
|
|
|
printf " %-16s - Show all of the above\\n" help-boards; \
|
|
|
|
|
echo '')
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
@echo ' make V=0|1 [targets] 0 => quiet build (default), 1 => verbose build'
|
2006-08-08 19:35:14 +00:00
|
|
|
@echo ' make V=2 [targets] 2 => give reason for rebuild of target'
|
2005-04-16 22:20:36 +00:00
|
|
|
@echo ' make O=dir [targets] Locate all output files in "dir", including .config'
|
2019-10-25 11:52:32 +00:00
|
|
|
@echo ' make C=1 [targets] Check re-compiled c source with $$CHECK'
|
|
|
|
|
@echo ' (sparse by default)'
|
2006-05-23 20:57:23 +00:00
|
|
|
@echo ' make C=2 [targets] Force check of all c source with $$CHECK'
|
2011-06-16 11:26:23 +00:00
|
|
|
@echo ' make RECORDMCOUNT_WARN=1 [targets] Warn about ignored mcount sections'
|
2019-08-31 16:25:55 +00:00
|
|
|
@echo ' make W=n [targets] Enable extra build checks, n=1,2,3 where'
|
2011-04-27 20:15:27 +00:00
|
|
|
@echo ' 1: warnings which may be relevant and do not occur too often'
|
|
|
|
|
@echo ' 2: warnings which occur quite often but may still be relevant'
|
|
|
|
|
@echo ' 3: more obscure warnings, can most likely be ignored'
|
2011-04-29 12:45:31 +00:00
|
|
|
@echo ' Multiple levels can be combined with W=12 or W=123'
|
2005-04-16 22:20:36 +00:00
|
|
|
@echo ''
|
|
|
|
|
@echo 'Execute "make" or "make all" to build all targets marked with [*] '
|
|
|
|
|
@echo 'For further info see the ./README file'
|
|
|
|
|
|
|
|
|
|
|
2008-04-06 20:16:07 +00:00
|
|
|
help-board-dirs := $(addprefix help-,$(board-dirs))
|
|
|
|
|
|
|
|
|
|
help-boards: $(help-board-dirs)
|
|
|
|
|
|
2014-11-28 12:31:43 +00:00
|
|
|
boards-per-dir = $(sort $(notdir $(wildcard $(srctree)/arch/$(SRCARCH)/configs/$*/*_defconfig)))
|
2008-04-06 20:16:07 +00:00
|
|
|
|
|
|
|
|
$(help-board-dirs): help-%:
|
|
|
|
|
@echo 'Architecture specific targets ($(SRCARCH) $*):'
|
|
|
|
|
@$(if $(boards-per-dir), \
|
|
|
|
|
$(foreach b, $(boards-per-dir), \
|
|
|
|
|
printf " %-24s - Build for %s\\n" $*/$(b) $(subst _defconfig,,$(b));) \
|
|
|
|
|
echo '')
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# Documentation targets
|
|
|
|
|
# ---------------------------------------------------------------------------
|
2017-10-09 15:26:15 +00:00
|
|
|
DOC_TARGETS := xmldocs latexdocs pdfdocs htmldocs epubdocs cleandocs \
|
|
|
|
|
linkcheckdocs dochelp refcheckdocs
|
Documentation/sphinx: add basic working Sphinx configuration and build
Add basic configuration and makefile to build documentation from any
.rst files under Documentation using Sphinx. For starters, there's just
the placeholder index.rst.
At the top level Makefile, hook Sphinx documentation targets alongside
(but independent of) the DocBook toolchain, having both be run on the
various 'make *docs' targets.
All Sphinx processing is placed into Documentation/Makefile.sphinx. Both
that and the Documentation/DocBook/Makefile are now expected to handle
all the documentation targets, explicitly ignoring them if they're not
relevant for that particular toolchain. The changes to the existing
DocBook Makefile are kept minimal.
There is graceful handling of missing Sphinx and rst2pdf (which is
needed for pdf output) by checking for the tool and python module,
respectively, with informative messages to the user.
If the Read the Docs theme (sphinx_rtd_theme) is available, use it, but
otherwise gracefully fall back to the Sphinx default theme, with an
informative message to the user, and slightly less pretty HTML output.
Sphinx can now handle htmldocs, pdfdocs (if rst2pdf is available),
epubdocs and xmldocs targets. The output documents are written into per
output type subdirectories under Documentation/output.
Finally, you can pass options to sphinx-build using the SPHINXBUILD make
variable. For example, 'make SPHINXOPTS=-v htmldocs' for more verbose
output from Sphinx.
This is based on the original work by Jonathan Corbet, but he probably
wouldn't recognize this as his own anymore.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
2016-05-19 12:14:05 +00:00
|
|
|
PHONY += $(DOC_TARGETS)
|
2019-08-21 17:33:21 +00:00
|
|
|
$(DOC_TARGETS):
|
2017-05-14 14:50:01 +00:00
|
|
|
$(Q)$(MAKE) $(build)=Documentation $@
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-02-19 09:33:02 +00:00
|
|
|
# Misc
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
PHONY += scripts_gdb
|
2019-06-04 10:13:57 +00:00
|
|
|
scripts_gdb: prepare0
|
2019-02-19 09:33:04 +00:00
|
|
|
$(Q)$(MAKE) $(build)=scripts/gdb
|
2019-02-19 09:33:05 +00:00
|
|
|
$(Q)ln -fsn $(abspath $(srctree)/scripts/gdb/vmlinux-gdb.py)
|
2019-02-19 09:33:02 +00:00
|
|
|
|
|
|
|
|
ifdef CONFIG_GDB_SCRIPTS
|
|
|
|
|
all: scripts_gdb
|
|
|
|
|
endif
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
else # KBUILD_EXTMOD
|
|
|
|
|
|
|
|
|
|
###
|
|
|
|
|
# External module support.
|
|
|
|
|
# When building external modules the kernel used as basis is considered
|
|
|
|
|
# read-only, and no consistency checks are made and the make
|
|
|
|
|
# system is not used on the basis kernel. If updates are required
|
|
|
|
|
# in the basis kernel ordinary make commands (without M=...) must
|
|
|
|
|
# be used.
|
|
|
|
|
#
|
|
|
|
|
# The following are the only valid targets when building external
|
|
|
|
|
# modules.
|
|
|
|
|
# make M=dir clean Delete all automatically generated files
|
|
|
|
|
# make M=dir modules Make all modules in specified dir
|
|
|
|
|
# make M=dir Same as 'make M=dir modules'
|
|
|
|
|
# make M=dir modules_install
|
2006-06-24 22:07:55 +00:00
|
|
|
# Install the modules built in the module directory
|
2005-04-16 22:20:36 +00:00
|
|
|
# Assumes install directory is already created
|
|
|
|
|
|
|
|
|
|
# We are always building modules
|
|
|
|
|
KBUILD_MODULES := 1
|
|
|
|
|
|
2019-08-10 15:53:04 +00:00
|
|
|
build-dirs := $(KBUILD_EXTMOD)
|
|
|
|
|
PHONY += modules
|
2020-06-01 05:57:14 +00:00
|
|
|
modules: descend
|
2006-08-08 19:36:08 +00:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += modules_install
|
2006-01-28 22:51:57 +00:00
|
|
|
modules_install: _emodinst_ _emodinst_post
|
2006-02-14 14:58:15 +00:00
|
|
|
|
2006-03-05 22:14:10 +00:00
|
|
|
install-dir := $(if $(INSTALL_MOD_DIR),$(INSTALL_MOD_DIR),extra)
|
|
|
|
|
PHONY += _emodinst_
|
2006-01-28 22:51:57 +00:00
|
|
|
_emodinst_:
|
|
|
|
|
$(Q)mkdir -p $(MODLIB)/$(install-dir)
|
2006-08-08 19:36:08 +00:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modinst
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += _emodinst_post
|
2006-01-28 22:51:57 +00:00
|
|
|
_emodinst_post: _emodinst_
|
|
|
|
|
$(call cmd,depmod)
|
|
|
|
|
|
2019-08-10 15:53:05 +00:00
|
|
|
clean-dirs := $(KBUILD_EXTMOD)
|
2019-10-29 12:38:08 +00:00
|
|
|
clean: rm-files := $(KBUILD_EXTMOD)/Module.symvers $(KBUILD_EXTMOD)/modules.nsdeps
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2016-03-13 00:39:55 +00:00
|
|
|
PHONY += help
|
2005-04-16 22:20:36 +00:00
|
|
|
help:
|
|
|
|
|
@echo ' Building external modules.'
|
|
|
|
|
@echo ' Syntax: make -C path/to/kernel/src M=$$PWD target'
|
|
|
|
|
@echo ''
|
|
|
|
|
@echo ' modules - default target, build the module(s)'
|
|
|
|
|
@echo ' modules_install - install the module'
|
|
|
|
|
@echo ' clean - remove generated files in module directory only'
|
|
|
|
|
@echo ''
|
2006-01-25 06:13:18 +00:00
|
|
|
|
2018-11-29 03:56:30 +00:00
|
|
|
PHONY += prepare
|
2005-04-16 22:20:36 +00:00
|
|
|
endif # KBUILD_EXTMOD
|
|
|
|
|
|
2019-11-18 04:52:47 +00:00
|
|
|
# Single targets
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
# To build individual files in subdirectories, you can do like this:
|
|
|
|
|
#
|
|
|
|
|
# make foo/bar/baz.s
|
|
|
|
|
#
|
|
|
|
|
# The supported suffixes for single-target are listed in 'single-targets'
|
|
|
|
|
#
|
|
|
|
|
# To build only under specific subdirectories, you can do like this:
|
|
|
|
|
#
|
|
|
|
|
# make foo/bar/baz/
|
|
|
|
|
|
|
|
|
|
ifdef single-build
|
|
|
|
|
|
|
|
|
|
# .ko is special because modpost is needed
|
|
|
|
|
single-ko := $(sort $(filter %.ko, $(MAKECMDGOALS)))
|
|
|
|
|
single-no-ko := $(sort $(patsubst %.ko,%.mod, $(MAKECMDGOALS)))
|
|
|
|
|
|
|
|
|
|
$(single-ko): single_modpost
|
|
|
|
|
@:
|
|
|
|
|
$(single-no-ko): descend
|
|
|
|
|
@:
|
|
|
|
|
|
|
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
|
|
|
|
# For the single build of in-tree modules, use a temporary file to avoid
|
|
|
|
|
# the situation of modules_install installing an invalid modules.order.
|
|
|
|
|
MODORDER := .modules.tmp
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
PHONY += single_modpost
|
|
|
|
|
single_modpost: $(single-no-ko)
|
|
|
|
|
$(Q){ $(foreach m, $(single-ko), echo $(extmod-prefix)$m;) } > $(MODORDER)
|
|
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
|
|
|
|
|
|
|
|
|
|
KBUILD_MODULES := 1
|
|
|
|
|
|
|
|
|
|
export KBUILD_SINGLE_TARGETS := $(addprefix $(extmod-prefix), $(single-no-ko))
|
|
|
|
|
|
|
|
|
|
# trim unrelated directories
|
|
|
|
|
build-dirs := $(foreach d, $(build-dirs), \
|
|
|
|
|
$(if $(filter $(d)/%, $(KBUILD_SINGLE_TARGETS)), $(d)))
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2020-05-22 01:59:59 +00:00
|
|
|
ifndef CONFIG_MODULES
|
|
|
|
|
KBUILD_MODULES :=
|
|
|
|
|
endif
|
|
|
|
|
|
2019-08-10 15:53:04 +00:00
|
|
|
# Handle descending into subdirectories listed in $(build-dirs)
|
|
|
|
|
# Preset locale variables to speed up the build process. Limit locale
|
|
|
|
|
# tweaks to this spot to avoid wrong language settings when running
|
|
|
|
|
# make menuconfig etc.
|
|
|
|
|
# Error messages still appears in the original language
|
|
|
|
|
PHONY += descend $(build-dirs)
|
|
|
|
|
descend: $(build-dirs)
|
|
|
|
|
$(build-dirs): prepare
|
2019-11-18 04:52:47 +00:00
|
|
|
$(Q)$(MAKE) $(build)=$@ \
|
2020-02-05 06:51:52 +00:00
|
|
|
single-build=$(if $(filter-out $@/, $(filter $@/%, $(single-no-ko))),1) \
|
2019-11-18 04:52:47 +00:00
|
|
|
need-builtin=1 need-modorder=1
|
2019-08-10 15:53:04 +00:00
|
|
|
|
2019-08-10 15:53:05 +00:00
|
|
|
clean-dirs := $(addprefix _clean_, $(clean-dirs))
|
|
|
|
|
PHONY += $(clean-dirs) clean
|
|
|
|
|
$(clean-dirs):
|
|
|
|
|
$(Q)$(MAKE) $(clean)=$(patsubst _clean_%,%,$@)
|
|
|
|
|
|
2010-09-06 10:00:08 +00:00
|
|
|
clean: $(clean-dirs)
|
|
|
|
|
$(call cmd,rmfiles)
|
2011-05-10 22:47:16 +00:00
|
|
|
@find $(if $(KBUILD_EXTMOD), $(KBUILD_EXTMOD), .) $(RCS_FIND_IGNORE) \
|
2017-11-16 16:49:13 +00:00
|
|
|
\( -name '*.[aios]' -o -name '*.ko' -o -name '.*.cmd' \
|
2018-09-06 18:26:07 +00:00
|
|
|
-o -name '*.ko.*' \
|
|
|
|
|
-o -name '*.dtb' -o -name '*.dtb.S' -o -name '*.dt.yaml' \
|
2017-11-16 16:49:13 +00:00
|
|
|
-o -name '*.dwo' -o -name '*.lst' \
|
2019-10-29 12:38:07 +00:00
|
|
|
-o -name '*.su' -o -name '*.mod' \
|
2010-09-06 10:00:08 +00:00
|
|
|
-o -name '.*.d' -o -name '.*.tmp' -o -name '*.mod.c' \
|
2018-03-23 13:04:31 +00:00
|
|
|
-o -name '*.lex.c' -o -name '*.tab.[ch]' \
|
2018-03-23 13:04:37 +00:00
|
|
|
-o -name '*.asn1.[ch]' \
|
2010-09-06 10:00:08 +00:00
|
|
|
-o -name '*.symtypes' -o -name 'modules.order' \
|
kbuild: create modules.builtin without Makefile.modbuiltin or tristate.conf
Commit bc081dd6e9f6 ("kbuild: generate modules.builtin") added
infrastructure to generate modules.builtin, the list of all
builtin modules.
Basically, it works like this:
- Kconfig generates include/config/tristate.conf, the list of
tristate CONFIG options with a value in a capital letter.
- scripts/Makefile.modbuiltin makes Kbuild descend into
directories to collect the information of builtin modules.
I am not a big fan of it because Kbuild ends up with traversing
the source tree twice.
I am not sure how perfectly it should work, but this approach cannot
avoid false positives; even if the relevant CONFIG option is tristate,
some Makefiles forces obj-m to obj-y.
Some examples are:
arch/powerpc/platforms/powermac/Makefile:
obj-$(CONFIG_NVRAM:m=y) += nvram.o
net/ipv6/Makefile:
obj-$(subst m,y,$(CONFIG_IPV6)) += inet6_hashtables.o
net/netlabel/Makefile:
obj-$(subst m,y,$(CONFIG_IPV6)) += netlabel_calipso.o
Nobody has complained about (or noticed) it, so it is probably fine to
have false positives in modules.builtin.
This commit simplifies the implementation. Let's exploit the fact
that every module has MODULE_LICENSE(). (modpost shows a warning if
MODULE_LICENSE is missing. If so, 0-day bot would already have blocked
such a module.)
I added MODULE_FILE to <linux/module.h>. When the code is being compiled
as builtin, it will be filled with the file path of the module, and
collected into modules.builtin.info. Then, scripts/link-vmlinux.sh
extracts the list of builtin modules out of it.
This new approach fixes the false-positives above, but adds another
type of false-positives; non-modular code may have MODULE_LICENSE()
by mistake. This is not a big deal, it is just the code is always
orphan. We can clean it up if we like. You can see cleanup examples by:
$ git log --grep='make.* explicitly non-modular'
To sum up, this commits deletes lots of code, but still produces almost
equivalent results. Please note it does not increase the vmlinux size at
all. As you can see in include/asm-generic/vmlinux.lds.h, the .modinfo
section is discarded in the link stage.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2019-12-19 08:33:29 +00:00
|
|
|
-o -name '.tmp_*.o.*' \
|
2016-05-23 22:09:38 +00:00
|
|
|
-o -name '*.c.[012]*.*' \
|
2017-04-24 20:04:58 +00:00
|
|
|
-o -name '*.ll' \
|
2010-09-06 10:00:08 +00:00
|
|
|
-o -name '*.gcno' \) -type f -print | xargs rm -f
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# Generate tags for editors
|
|
|
|
|
# ---------------------------------------------------------------------------
|
2008-12-03 21:24:13 +00:00
|
|
|
quiet_cmd_tags = GEN $@
|
2019-08-25 13:28:37 +00:00
|
|
|
cmd_tags = $(BASH) $(srctree)/scripts/tags.sh $@
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2011-01-14 12:07:05 +00:00
|
|
|
tags TAGS cscope gtags: FORCE
|
2005-04-16 22:20:36 +00:00
|
|
|
$(call cmd,tags)
|
|
|
|
|
|
2019-09-06 10:32:32 +00:00
|
|
|
# Script to generate missing namespace dependencies
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
PHONY += nsdeps
|
2019-10-29 12:38:06 +00:00
|
|
|
nsdeps: export KBUILD_NSDEPS=1
|
2019-09-06 10:32:32 +00:00
|
|
|
nsdeps: modules
|
2019-10-29 12:38:06 +00:00
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/nsdeps
|
2019-09-06 10:32:32 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# Scripts to check various things for consistency
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
2011-04-26 21:15:01 +00:00
|
|
|
PHONY += includecheck versioncheck coccicheck namespacecheck export_report
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
includecheck:
|
2011-04-26 21:18:29 +00:00
|
|
|
find $(srctree)/* $(RCS_FIND_IGNORE) \
|
2005-04-16 22:20:36 +00:00
|
|
|
-name '*.[hcS]' -type f -print | sort \
|
2007-11-05 10:51:44 +00:00
|
|
|
| xargs $(PERL) -w $(srctree)/scripts/checkincludes.pl
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
versioncheck:
|
2011-04-26 21:19:28 +00:00
|
|
|
find $(srctree)/* $(RCS_FIND_IGNORE) \
|
2005-04-16 22:20:36 +00:00
|
|
|
-name '*.[hcS]' -type f -print | sort \
|
2007-11-05 10:51:44 +00:00
|
|
|
| xargs $(PERL) -w $(srctree)/scripts/checkversion.pl
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2010-06-06 15:15:01 +00:00
|
|
|
coccicheck:
|
2019-08-25 13:28:37 +00:00
|
|
|
$(Q)$(BASH) $(srctree)/scripts/$@
|
2010-06-06 15:15:01 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
namespacecheck:
|
|
|
|
|
$(PERL) $(srctree)/scripts/namespace.pl
|
|
|
|
|
|
2007-08-24 21:04:56 +00:00
|
|
|
export_report:
|
|
|
|
|
$(PERL) $(srctree)/scripts/export_report.pl
|
|
|
|
|
|
2013-06-24 12:48:37 +00:00
|
|
|
PHONY += checkstack kernelrelease kernelversion image_name
|
2006-09-27 08:50:37 +00:00
|
|
|
|
2006-12-13 08:34:12 +00:00
|
|
|
# UML needs a little special treatment here. It wants to use the host
|
|
|
|
|
# toolchain, so needs $(SUBARCH) passed to checkstack.pl. Everyone
|
|
|
|
|
# else wants $(ARCH), including people doing cross-builds, which means
|
|
|
|
|
# that $(SUBARCH) doesn't work here.
|
|
|
|
|
ifeq ($(ARCH), um)
|
|
|
|
|
CHECKSTACK_ARCH := $(SUBARCH)
|
|
|
|
|
else
|
|
|
|
|
CHECKSTACK_ARCH := $(ARCH)
|
|
|
|
|
endif
|
2005-04-16 22:20:36 +00:00
|
|
|
checkstack:
|
|
|
|
|
$(OBJDUMP) -d vmlinux $$(find . -name '*.ko') | \
|
2019-07-06 03:07:11 +00:00
|
|
|
$(PERL) $(srctree)/scripts/checkstack.pl $(CHECKSTACK_ARCH)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2010-08-20 09:36:06 +00:00
|
|
|
kernelrelease:
|
|
|
|
|
@echo "$(KERNELVERSION)$$($(CONFIG_SHELL) $(srctree)/scripts/setlocalversion $(srctree))"
|
2010-06-28 02:45:21 +00:00
|
|
|
|
2006-01-09 20:20:34 +00:00
|
|
|
kernelversion:
|
2006-01-16 11:12:12 +00:00
|
|
|
@echo $(KERNELVERSION)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2013-06-24 12:48:37 +00:00
|
|
|
image_name:
|
|
|
|
|
@echo $(KBUILD_IMAGE)
|
|
|
|
|
|
2012-04-11 16:36:18 +00:00
|
|
|
# Clear a bunch of variables before executing the submake
|
2019-02-22 07:40:06 +00:00
|
|
|
|
|
|
|
|
ifeq ($(quiet),silent_)
|
|
|
|
|
tools_silent=s
|
|
|
|
|
endif
|
|
|
|
|
|
2012-04-11 16:36:18 +00:00
|
|
|
tools/: FORCE
|
2012-11-05 21:02:08 +00:00
|
|
|
$(Q)mkdir -p $(objtree)/tools
|
2019-07-06 03:07:11 +00:00
|
|
|
$(Q)$(MAKE) LDFLAGS= MAKEFLAGS="$(tools_silent) $(filter --j% -j,$(MAKEFLAGS))" O=$(abspath $(objtree)) subdir=tools -C $(srctree)/tools/
|
2012-04-11 16:36:18 +00:00
|
|
|
|
|
|
|
|
tools/%: FORCE
|
2012-11-05 21:02:08 +00:00
|
|
|
$(Q)mkdir -p $(objtree)/tools
|
2019-07-06 03:07:11 +00:00
|
|
|
$(Q)$(MAKE) LDFLAGS= MAKEFLAGS="$(tools_silent) $(filter --j% -j,$(MAKEFLAGS))" O=$(abspath $(objtree)) subdir=tools -C $(srctree)/tools/ $*
|
2012-04-11 16:36:18 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
quiet_cmd_rmfiles = $(if $(wildcard $(rm-files)),CLEAN $(wildcard $(rm-files)))
|
2020-05-04 08:08:07 +00:00
|
|
|
cmd_rmfiles = rm -rf $(rm-files)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-04-21 22:53:56 +00:00
|
|
|
# Run depmod only if we have System.map and depmod is executable
|
2007-10-18 19:24:21 +00:00
|
|
|
quiet_cmd_depmod = DEPMOD $(KERNELRELEASE)
|
2011-06-15 20:15:47 +00:00
|
|
|
cmd_depmod = $(CONFIG_SHELL) $(srctree)/scripts/depmod.sh $(DEPMOD) \
|
2018-05-09 07:23:48 +00:00
|
|
|
$(KERNELRELEASE)
|
2007-10-18 19:24:21 +00:00
|
|
|
|
kbuild: let fixdep directly write to .*.cmd files
Currently, fixdep writes dependencies to .*.tmp, which is renamed to
.*.cmd after everything succeeds. This is a very safe way to avoid
corrupted .*.cmd files. The if_changed_dep has carried this safety
mechanism since it was added in 2002.
If fixdep fails for some reasons or a user terminates the build while
fixdep is running, the incomplete output from the fixdep could be
troublesome.
This is my insight about some bad scenarios:
[1] If the compiler succeeds to generate *.o file, but fixdep fails
to write necessary dependencies to .*.cmd file, Make will miss
to rebuild the object when headers or CONFIG options are changed.
In this case, fixdep should not generate .*.cmd file at all so
that 'arg-check' will surely trigger the rebuild of the object.
[2] A partially constructed .*.cmd file may not be a syntactically
correct makefile. The next time Make runs, it would include it,
then fail to parse it. Once this happens, 'make clean' is be the
only way to fix it.
In fact, [1] is no longer a problem since commit 9c2af1c7377a ("kbuild:
add .DELETE_ON_ERROR special target"). Make deletes a target file on
any failure in its recipe. Because fixdep is a part of the recipe of
*.o target, if it fails, the *.o is deleted anyway. However, I am a
bit worried about the slight possibility of [2].
So, here is a solution. Let fixdep directly write to a .*.cmd file,
but allow makefiles to include it only when its corresponding target
exists.
This effectively reverts commit 2982c953570b ("kbuild: remove redundant
$(wildcard ...) for cmd_files calculation"), and commit 00d78ab2ba75
("kbuild: remove dead code in cmd_files calculation in top Makefile")
because now we must check the presence of targets.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2018-11-30 01:05:22 +00:00
|
|
|
# read saved command lines for existing targets
|
|
|
|
|
existing-targets := $(wildcard $(sort $(targets)))
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-02-22 07:40:08 +00:00
|
|
|
-include $(foreach f,$(existing-targets),$(dir $(f)).$(notdir $(f)).cmd)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-02-29 16:09:58 +00:00
|
|
|
endif # config-build
|
2019-08-10 15:53:03 +00:00
|
|
|
endif # mixed-build
|
|
|
|
|
endif # need-sub-make
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-03-05 22:14:10 +00:00
|
|
|
PHONY += FORCE
|
2005-04-16 22:20:36 +00:00
|
|
|
FORCE:
|
2006-03-05 22:14:10 +00:00
|
|
|
|
2018-07-05 03:33:07 +00:00
|
|
|
# Declare the contents of the PHONY variable as phony. We keep that
|
2009-04-09 11:34:34 +00:00
|
|
|
# information in a variable so we can use it in if_changed and friends.
|
2006-03-05 22:14:10 +00:00
|
|
|
.PHONY: $(PHONY)
|
