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 22:07:57 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
Linux 4.0-rc1
.. after extensive statistical analysis of my G+ polling, I've come to
the inescapable conclusion that internet polls are bad.
Big surprise.
But "Hurr durr I'ma sheep" trounced "I like online polls" by a 62-to-38%
margin, in a poll that people weren't even supposed to participate in.
Who can argue with solid numbers like that? 5,796 votes from people who
can't even follow the most basic directions?
In contrast, "v4.0" beat out "v3.20" by a slimmer margin of 56-to-44%,
but with a total of 29,110 votes right now.
Now, arguably, that vote spread is only about 3,200 votes, which is less
than the almost six thousand votes that the "please ignore" poll got, so
it could be considered noise.
But hey, I asked, so I'll honor the votes.
2015-02-23 10:21:14 +08:00
|
|
|
VERSION = 4
|
2018-04-16 09:24:20 +08:00
|
|
|
PATCHLEVEL = 17
|
2011-05-30 08:43:36 +08:00
|
|
|
SUBLEVEL = 0
|
2018-06-04 05:15:21 +08:00
|
|
|
EXTRAVERSION =
|
2018-05-07 10:57:38 +08:00
|
|
|
NAME = Merciless Moray
|
2005-04-17 06:20:36 +08: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.
|
|
|
|
|
|
2017-10-04 11:56:05 +08:00
|
|
|
# That's our default target when none is given on the command line
|
|
|
|
|
PHONY := _all
|
|
|
|
|
_all:
|
|
|
|
|
|
2015-03-27 19:43:36 +08:00
|
|
|
# o Do not use make's built-in rules and variables
|
|
|
|
|
# (this increases performance and avoids hard-to-debug behaviour);
|
|
|
|
|
# o Look for make include files relative to root of kernel src
|
|
|
|
|
MAKEFLAGS += -rR --include-dir=$(CURDIR)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-12-17 22:56:11 +08:00
|
|
|
# Avoid funny character set dependencies
|
2009-12-18 07:51:37 +08:00
|
|
|
unexport LC_ALL
|
2009-12-17 22:56:11 +08:00
|
|
|
LC_COLLATE=C
|
|
|
|
|
LC_NUMERIC=C
|
2010-01-08 19:25:37 +08:00
|
|
|
export LC_COLLATE LC_NUMERIC
|
2009-12-17 22:56:11 +08:00
|
|
|
|
2013-11-11 22:27:43 +08:00
|
|
|
# Avoid interference with shell env settings
|
|
|
|
|
unexport GREP_OPTIONS
|
|
|
|
|
|
2005-04-17 06:20:36 +08: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 22:25:04 +08:00
|
|
|
# unavoidable when linking the built-in.a targets which finally
|
2005-04-17 06:20:36 +08: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.
|
|
|
|
|
|
2014-07-04 20:29:30 +08: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.
|
|
|
|
|
#
|
2005-04-17 06:20:36 +08:00
|
|
|
# To put more focus on warnings, be less verbose as default
|
|
|
|
|
# Use 'make V=1' to see the full commands
|
|
|
|
|
|
2009-05-26 16:03:07 +08:00
|
|
|
ifeq ("$(origin V)", "command line")
|
|
|
|
|
KBUILD_VERBOSE = $(V)
|
2005-04-17 06:20:36 +08:00
|
|
|
endif
|
|
|
|
|
ifndef KBUILD_VERBOSE
|
|
|
|
|
KBUILD_VERBOSE = 0
|
|
|
|
|
endif
|
|
|
|
|
|
2014-07-04 20:29:30 +08: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 19:42:30 +08:00
|
|
|
ifneq ($(findstring s,$(filter-out --%,$(MAKEFLAGS))),)
|
2014-07-04 20:29:30 +08:00
|
|
|
quiet=silent_
|
2017-01-19 12:16:55 +08:00
|
|
|
tools_silent=s
|
2014-07-04 20:29:30 +08:00
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
export quiet Q KBUILD_VERBOSE
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# kbuild supports saving output files in a separate directory.
|
|
|
|
|
# To locate output files in a separate directory two syntaxes are supported.
|
|
|
|
|
# In both cases the working directory must be the root of the kernel src.
|
|
|
|
|
# 1) O=
|
|
|
|
|
# Use "make O=dir/to/store/output/files/"
|
2006-06-25 06:07:55 +08:00
|
|
|
#
|
2005-04-17 06:20:36 +08:00
|
|
|
# 2) Set KBUILD_OUTPUT
|
|
|
|
|
# Set the environment variable KBUILD_OUTPUT to point to the directory
|
|
|
|
|
# where the output files shall be placed.
|
|
|
|
|
# export KBUILD_OUTPUT=dir/to/store/output/files/
|
|
|
|
|
# make
|
|
|
|
|
#
|
|
|
|
|
# The O= assignment takes precedence over the KBUILD_OUTPUT environment
|
|
|
|
|
# variable.
|
|
|
|
|
|
2017-06-30 10:45:43 +08:00
|
|
|
# KBUILD_SRC is not intended to be used by the regular user (for now),
|
|
|
|
|
# it is set on invocation of make with KBUILD_OUTPUT or O= specified.
|
2005-04-17 06:20:36 +08:00
|
|
|
ifeq ($(KBUILD_SRC),)
|
|
|
|
|
|
|
|
|
|
# OK, Make called in directory where kernel src resides
|
|
|
|
|
# Do we want to locate output files in a separate directory?
|
2009-05-26 16:03:07 +08:00
|
|
|
ifeq ("$(origin O)", "command line")
|
|
|
|
|
KBUILD_OUTPUT := $(O)
|
2005-04-17 06:20:36 +08:00
|
|
|
endif
|
|
|
|
|
|
2007-12-07 05:20:11 +08:00
|
|
|
# Cancel implicit rules on top Makefile
|
|
|
|
|
$(CURDIR)/Makefile Makefile: ;
|
|
|
|
|
|
2016-04-03 03:38:53 +08:00
|
|
|
ifneq ($(words $(subst :, ,$(CURDIR))), 1)
|
|
|
|
|
$(error main directory cannot contain spaces nor colons)
|
|
|
|
|
endif
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
ifneq ($(KBUILD_OUTPUT),)
|
|
|
|
|
# check that the output directory actually exists
|
|
|
|
|
saved-output := $(KBUILD_OUTPUT)
|
2017-10-02 16:07:28 +08:00
|
|
|
KBUILD_OUTPUT := $(shell mkdir -p $(KBUILD_OUTPUT) && cd $(KBUILD_OUTPUT) \
|
2017-11-05 17:44:16 +08:00
|
|
|
&& pwd)
|
2005-04-17 06:20:36 +08:00
|
|
|
$(if $(KBUILD_OUTPUT),, \
|
2014-03-31 15:41:36 +08:00
|
|
|
$(error failed to create output directory "$(saved-output)"))
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-09-22 07:09:02 +08:00
|
|
|
PHONY += $(MAKECMDGOALS) sub-make
|
|
|
|
|
|
2007-12-07 05:20:11 +08:00
|
|
|
$(filter-out _all sub-make $(CURDIR)/Makefile, $(MAKECMDGOALS)) _all: sub-make
|
2012-10-15 20:49:12 +08:00
|
|
|
@:
|
2007-09-22 07:09:02 +08:00
|
|
|
|
2017-06-30 10:45:43 +08:00
|
|
|
# Invoke a second make in the output directory, passing relevant variables
|
2016-03-13 08:13:55 +08:00
|
|
|
sub-make:
|
2014-09-09 19:02:23 +08:00
|
|
|
$(Q)$(MAKE) -C $(KBUILD_OUTPUT) KBUILD_SRC=$(CURDIR) \
|
2014-09-09 19:02:24 +08:00
|
|
|
-f $(CURDIR)/Makefile $(filter-out _all sub-make,$(MAKECMDGOALS))
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# Leave processing to above invocation of make
|
|
|
|
|
skip-makefile := 1
|
|
|
|
|
endif # ifneq ($(KBUILD_OUTPUT),)
|
|
|
|
|
endif # ifeq ($(KBUILD_SRC),)
|
|
|
|
|
|
|
|
|
|
# We process the rest of the Makefile if this is the final invocation of make
|
|
|
|
|
ifeq ($(skip-makefile),)
|
|
|
|
|
|
2014-09-09 19:02:22 +08: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 19:02:24 +08: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 17:03:17 +08:00
|
|
|
# See the file "Documentation/dev-tools/sparse.rst" for more details,
|
|
|
|
|
# including where to get the "sparse" utility.
|
2014-09-09 19:02:24 +08:00
|
|
|
|
|
|
|
|
ifeq ("$(origin C)", "command line")
|
|
|
|
|
KBUILD_CHECKSRC = $(C)
|
|
|
|
|
endif
|
|
|
|
|
ifndef KBUILD_CHECKSRC
|
|
|
|
|
KBUILD_CHECKSRC = 0
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# Use make M=dir to specify directory of external module to build
|
|
|
|
|
# Old syntax make ... SUBDIRS=$PWD is still supported
|
|
|
|
|
# Setting the environment variable KBUILD_EXTMOD take precedence
|
|
|
|
|
ifdef SUBDIRS
|
|
|
|
|
KBUILD_EXTMOD ?= $(SUBDIRS)
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
ifeq ("$(origin M)", "command line")
|
|
|
|
|
KBUILD_EXTMOD := $(M)
|
|
|
|
|
endif
|
|
|
|
|
|
2014-04-26 05:25:18 +08:00
|
|
|
ifeq ($(KBUILD_SRC),)
|
|
|
|
|
# building in the source tree
|
|
|
|
|
srctree := .
|
|
|
|
|
else
|
|
|
|
|
ifeq ($(KBUILD_SRC)/,$(dir $(CURDIR)))
|
|
|
|
|
# building in a subdirectory of the source tree
|
|
|
|
|
srctree := ..
|
|
|
|
|
else
|
|
|
|
|
srctree := $(KBUILD_SRC)
|
|
|
|
|
endif
|
|
|
|
|
endif
|
2017-10-04 11:56:06 +08:00
|
|
|
|
|
|
|
|
export KBUILD_CHECKSRC KBUILD_EXTMOD KBUILD_SRC
|
|
|
|
|
|
2014-04-25 23:29:45 +08:00
|
|
|
objtree := .
|
2005-04-17 06:20:36 +08:00
|
|
|
src := $(srctree)
|
|
|
|
|
obj := $(objtree)
|
|
|
|
|
|
2006-02-19 20:50:37 +08:00
|
|
|
VPATH := $(srctree)$(if $(KBUILD_EXTMOD),:$(KBUILD_EXTMOD))
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-06-19 15:40:26 +08:00
|
|
|
export srctree objtree VPATH
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2017-10-04 11:56:06 +08: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 16:40:29 +08:00
|
|
|
clean-targets := %clean mrproper cleandocs
|
|
|
|
|
no-dot-config-targets := $(clean-targets) \
|
2017-10-04 11:56:06 +08:00
|
|
|
cscope gtags TAGS tags help% %docs check% coccicheck \
|
|
|
|
|
$(version_h) headers_% archheaders archscripts \
|
|
|
|
|
kernelversion %src-pkg
|
|
|
|
|
|
|
|
|
|
config-targets := 0
|
|
|
|
|
mixed-targets := 0
|
|
|
|
|
dot-config := 1
|
|
|
|
|
|
|
|
|
|
ifneq ($(filter $(no-dot-config-targets), $(MAKECMDGOALS)),)
|
|
|
|
|
ifeq ($(filter-out $(no-dot-config-targets), $(MAKECMDGOALS)),)
|
|
|
|
|
dot-config := 0
|
|
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
|
|
|
|
ifneq ($(filter config %config,$(MAKECMDGOALS)),)
|
|
|
|
|
config-targets := 1
|
|
|
|
|
ifneq ($(words $(MAKECMDGOALS)),1)
|
|
|
|
|
mixed-targets := 1
|
|
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
endif
|
2018-02-11 16:40:29 +08:00
|
|
|
|
|
|
|
|
# For "make -j clean all", "make -j mrproper defconfig all", etc.
|
|
|
|
|
ifneq ($(filter $(clean-targets),$(MAKECMDGOALS)),)
|
|
|
|
|
ifneq ($(filter-out $(clean-targets),$(MAKECMDGOALS)),)
|
|
|
|
|
mixed-targets := 1
|
|
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
2017-10-04 11:56:06 +08:00
|
|
|
# install and modules_install need also be processed one by one
|
|
|
|
|
ifneq ($(filter install,$(MAKECMDGOALS)),)
|
|
|
|
|
ifneq ($(filter modules_install,$(MAKECMDGOALS)),)
|
|
|
|
|
mixed-targets := 1
|
|
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
ifeq ($(mixed-targets),1)
|
|
|
|
|
# ===========================================================================
|
|
|
|
|
# We're called with mixed targets (*config and build targets).
|
|
|
|
|
# Handle them one by one.
|
|
|
|
|
|
|
|
|
|
PHONY += $(MAKECMDGOALS) __build_one_by_one
|
|
|
|
|
|
|
|
|
|
$(filter-out __build_one_by_one, $(MAKECMDGOALS)): __build_one_by_one
|
|
|
|
|
@:
|
|
|
|
|
|
|
|
|
|
__build_one_by_one:
|
|
|
|
|
$(Q)set -e; \
|
|
|
|
|
for i in $(MAKECMDGOALS); do \
|
|
|
|
|
$(MAKE) -f $(srctree)/Makefile $$i; \
|
|
|
|
|
done
|
|
|
|
|
|
|
|
|
|
else
|
|
|
|
|
|
|
|
|
|
# We need some generic definitions (do not try to remake the file).
|
|
|
|
|
scripts/Kbuild.include: ;
|
|
|
|
|
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
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# SUBARCH tells the usermode build what the underlying arch is. That is set
|
|
|
|
|
# first, and if a usermode build is happening, the "ARCH=um" on the command
|
|
|
|
|
# line overrides the setting of ARCH below. If a native build is happening,
|
2014-04-28 15:26:18 +08:00
|
|
|
# then ARCH is assigned, getting whatever value it gets normally, and
|
2005-04-17 06:20:36 +08:00
|
|
|
# SUBARCH is subsequently ignored.
|
|
|
|
|
|
2012-12-21 05:51:55 +08:00
|
|
|
SUBARCH := $(shell uname -m | sed -e s/i.86/x86/ -e s/x86_64/x86/ \
|
|
|
|
|
-e s/sun4u/sparc64/ \
|
2005-04-17 06:20:36 +08:00
|
|
|
-e s/arm.*/arm/ -e s/sa110/arm/ \
|
2005-11-12 06:27:32 +08:00
|
|
|
-e s/s390x/s390/ -e s/parisc64/parisc/ \
|
2007-11-02 11:22:47 +08:00
|
|
|
-e s/ppc.*/powerpc/ -e s/mips.*/mips/ \
|
2017-07-11 09:08:08 +08:00
|
|
|
-e s/sh[234].*/sh/ -e s/aarch64.*/arm64/ \
|
|
|
|
|
-e s/riscv.*/riscv/)
|
2005-04-17 06:20:36 +08: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.
|
2009-12-22 08:24:06 +08:00
|
|
|
# A third alternative is to store a setting in .config so that plain
|
|
|
|
|
# "make" in the configured kernel build directory always uses that.
|
2005-04-17 06:20:36 +08:00
|
|
|
# Default value for CROSS_COMPILE is not to prefix executables
|
|
|
|
|
# Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
|
2009-10-12 05:22:58 +08:00
|
|
|
ARCH ?= $(SUBARCH)
|
2009-12-22 08:24:06 +08:00
|
|
|
CROSS_COMPILE ?= $(CONFIG_CROSS_COMPILE:"%"=%)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# Architecture as present in compile.h
|
2007-10-11 17:11:36 +08:00
|
|
|
UTS_MACHINE := $(ARCH)
|
|
|
|
|
SRCARCH := $(ARCH)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-11-13 03:14:19 +08:00
|
|
|
# Additional ARCH settings for x86
|
|
|
|
|
ifeq ($(ARCH),i386)
|
|
|
|
|
SRCARCH := x86
|
|
|
|
|
endif
|
|
|
|
|
ifeq ($(ARCH),x86_64)
|
|
|
|
|
SRCARCH := x86
|
|
|
|
|
endif
|
2007-10-26 01:42:04 +08:00
|
|
|
|
2008-12-03 15:17:12 +08:00
|
|
|
# Additional ARCH settings for sparc
|
2010-10-25 13:48:23 +08:00
|
|
|
ifeq ($(ARCH),sparc32)
|
|
|
|
|
SRCARCH := sparc
|
|
|
|
|
endif
|
2008-07-28 05:00:59 +08:00
|
|
|
ifeq ($(ARCH),sparc64)
|
2008-12-03 15:17:12 +08:00
|
|
|
SRCARCH := sparc
|
2008-07-28 05:00:59 +08:00
|
|
|
endif
|
2008-06-21 06:24:17 +08:00
|
|
|
|
2009-04-11 07:39:27 +08:00
|
|
|
# Additional ARCH settings for sh
|
|
|
|
|
ifeq ($(ARCH),sh64)
|
|
|
|
|
SRCARCH := sh
|
|
|
|
|
endif
|
|
|
|
|
|
2006-06-09 13:12:51 +08:00
|
|
|
KCONFIG_CONFIG ?= .config
|
2010-12-15 00:39:44 +08:00
|
|
|
export KCONFIG_CONFIG
|
2006-06-09 13:12:51 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# SHELL used by kbuild
|
|
|
|
|
CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
|
|
|
|
|
else if [ -x /bin/bash ]; then echo /bin/bash; \
|
|
|
|
|
else echo sh; fi ; fi)
|
|
|
|
|
|
2017-07-10 02:02:36 +08:00
|
|
|
HOST_LFS_CFLAGS := $(shell getconf LFS_CFLAGS)
|
|
|
|
|
HOST_LFS_LDFLAGS := $(shell getconf LFS_LDFLAGS)
|
|
|
|
|
HOST_LFS_LIBS := $(shell getconf LFS_LIBS)
|
|
|
|
|
|
2006-06-25 06:07:55 +08:00
|
|
|
HOSTCC = gcc
|
|
|
|
|
HOSTCXX = g++
|
2017-07-10 02:02:36 +08:00
|
|
|
HOSTCFLAGS := -Wall -Wmissing-prototypes -Wstrict-prototypes -O2 \
|
|
|
|
|
-fomit-frame-pointer -std=gnu89 $(HOST_LFS_CFLAGS)
|
|
|
|
|
HOSTCXXFLAGS := -O2 $(HOST_LFS_CFLAGS)
|
|
|
|
|
HOSTLDFLAGS := $(HOST_LFS_LDFLAGS)
|
|
|
|
|
HOST_LOADLIBES := $(HOST_LFS_LIBS)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# Make variables (CC, etc...)
|
|
|
|
|
AS = $(CROSS_COMPILE)as
|
|
|
|
|
LD = $(CROSS_COMPILE)ld
|
|
|
|
|
CC = $(CROSS_COMPILE)gcc
|
|
|
|
|
CPP = $(CC) -E
|
|
|
|
|
AR = $(CROSS_COMPILE)ar
|
|
|
|
|
NM = $(CROSS_COMPILE)nm
|
|
|
|
|
STRIP = $(CROSS_COMPILE)strip
|
|
|
|
|
OBJCOPY = $(CROSS_COMPILE)objcopy
|
|
|
|
|
OBJDUMP = $(CROSS_COMPILE)objdump
|
2017-12-10 00:02:28 +08:00
|
|
|
LEX = flex
|
|
|
|
|
YACC = bison
|
2005-04-17 06:20:36 +08:00
|
|
|
AWK = awk
|
|
|
|
|
GENKSYMS = scripts/genksyms/genksyms
|
2009-07-21 03:37:11 +08:00
|
|
|
INSTALLKERNEL := installkernel
|
2005-04-17 06:20:36 +08:00
|
|
|
DEPMOD = /sbin/depmod
|
|
|
|
|
PERL = perl
|
2014-07-18 12:40:11 +08: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 17:12:02 +08:00
|
|
|
PYTHON2 = python2
|
|
|
|
|
PYTHON3 = python3
|
2005-04-17 06:20:36 +08:00
|
|
|
CHECK = sparse
|
|
|
|
|
|
2008-12-28 05:38:44 +08:00
|
|
|
CHECKFLAGS := -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ \
|
2018-02-16 05:07:50 +08:00
|
|
|
-Wbitwise -Wno-return-void -Wno-unknown-attribute $(CF)
|
2016-06-07 17:57:02 +08: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 23:33:09 +08:00
|
|
|
CFLAGS_MODULE =
|
|
|
|
|
AFLAGS_MODULE =
|
|
|
|
|
LDFLAGS_MODULE =
|
2005-04-17 06:20:36 +08:00
|
|
|
CFLAGS_KERNEL =
|
|
|
|
|
AFLAGS_KERNEL =
|
2016-06-07 17:57:02 +08:00
|
|
|
LDFLAGS_vmlinux =
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2012-10-03 01:01:26 +08:00
|
|
|
# Use USERINCLUDE when you must reference the UAPI directories only.
|
|
|
|
|
USERINCLUDE := \
|
2017-10-04 11:56:04 +08:00
|
|
|
-I$(srctree)/arch/$(SRCARCH)/include/uapi \
|
|
|
|
|
-I$(objtree)/arch/$(SRCARCH)/include/generated/uapi \
|
2012-10-03 01:01:26 +08:00
|
|
|
-I$(srctree)/include/uapi \
|
2016-06-15 23:45:45 +08:00
|
|
|
-I$(objtree)/include/generated/uapi \
|
2012-10-03 01:01:26 +08:00
|
|
|
-include $(srctree)/include/linux/kconfig.h
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# Use LINUXINCLUDE when you must reference the include/ directory.
|
|
|
|
|
# Needed to be compatible with the O= option
|
2012-10-03 01:01:26 +08:00
|
|
|
LINUXINCLUDE := \
|
2017-10-04 11:56:04 +08:00
|
|
|
-I$(srctree)/arch/$(SRCARCH)/include \
|
|
|
|
|
-I$(objtree)/arch/$(SRCARCH)/include/generated \
|
2012-10-03 01:01:26 +08:00
|
|
|
$(if $(KBUILD_SRC), -I$(srctree)/include) \
|
2017-06-06 15:15:28 +08:00
|
|
|
-I$(objtree)/include \
|
|
|
|
|
$(USERINCLUDE)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
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 17:22:25 +08:00
|
|
|
KBUILD_AFLAGS := -D__ASSEMBLY__
|
2007-10-15 04:21:35 +08:00
|
|
|
KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
|
2017-07-26 21:36:23 +08:00
|
|
|
-fno-strict-aliasing -fno-common -fshort-wchar \
|
2009-06-15 13:54:02 +08:00
|
|
|
-Werror-implicit-function-declaration \
|
2014-10-20 17:23:12 +08: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 17:22:25 +08:00
|
|
|
-std=gnu89
|
|
|
|
|
KBUILD_CPPFLAGS := -D__KERNEL__
|
2010-07-29 01:11:27 +08: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 23:33:09 +08:00
|
|
|
KBUILD_AFLAGS_MODULE := -DMODULE
|
|
|
|
|
KBUILD_CFLAGS_MODULE := -DMODULE
|
|
|
|
|
KBUILD_LDFLAGS_MODULE := -T $(srctree)/scripts/module-common.lds
|
2018-03-16 15:37:09 +08:00
|
|
|
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 17:22:25 +08:00
|
|
|
GCC_PLUGINS_CFLAGS :=
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-11-17 22:37:31 +08:00
|
|
|
export ARCH SRCARCH CONFIG_SHELL HOSTCC HOSTCFLAGS CROSS_COMPILE AS LD CC
|
2017-07-10 02:02:36 +08:00
|
|
|
export CPP AR NM STRIP OBJCOPY OBJDUMP HOSTLDFLAGS HOST_LOADLIBES
|
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 17:12:02 +08:00
|
|
|
export MAKE LEX YACC AWK GENKSYMS INSTALLKERNEL PERL PYTHON PYTHON2 PYTHON3 UTS_MACHINE
|
2006-06-25 06:07:55 +08:00
|
|
|
export HOSTCXX HOSTCXXFLAGS LDFLAGS_MODULE CHECK CHECKFLAGS
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-16 04:17:25 +08:00
|
|
|
export KBUILD_CPPFLAGS NOSTDINC_FLAGS LINUXINCLUDE OBJCOPYFLAGS LDFLAGS
|
2018-02-07 07:36:00 +08:00
|
|
|
export KBUILD_CFLAGS CFLAGS_KERNEL CFLAGS_MODULE
|
|
|
|
|
export CFLAGS_KASAN CFLAGS_KASAN_NOSANITIZE CFLAGS_UBSAN
|
2007-10-16 03:59:31 +08: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 23:33:09 +08:00
|
|
|
export KBUILD_AFLAGS_MODULE KBUILD_CFLAGS_MODULE KBUILD_LDFLAGS_MODULE
|
2010-07-29 01:11:27 +08:00
|
|
|
export KBUILD_AFLAGS_KERNEL KBUILD_CFLAGS_KERNEL
|
2011-04-20 19:45:30 +08:00
|
|
|
export KBUILD_ARFLAGS
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# When compiling out-of-tree modules, put MODVERDIR in the module
|
|
|
|
|
# tree rather than in the kernel tree. The kernel tree might
|
|
|
|
|
# even be read-only.
|
|
|
|
|
export MODVERDIR := $(if $(KBUILD_EXTMOD),$(firstword $(KBUILD_EXTMOD))/).tmp_versions
|
|
|
|
|
|
|
|
|
|
# Files to ignore in find ... statements
|
|
|
|
|
|
2014-02-06 20:51:42 +08: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-17 05:49:15 +08:00
|
|
|
export RCS_TAR_IGNORE := --exclude SCCS --exclude BitKeeper --exclude .svn \
|
|
|
|
|
--exclude CVS --exclude .pc --exclude .hg --exclude .git
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# ===========================================================================
|
|
|
|
|
# Rules shared between *config targets and build targets
|
|
|
|
|
|
2017-08-02 10:31:06 +08:00
|
|
|
# Basic helpers built in scripts/basic/
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += scripts_basic
|
2005-04-17 06:20:36 +08:00
|
|
|
scripts_basic:
|
|
|
|
|
$(Q)$(MAKE) $(build)=scripts/basic
|
2009-11-17 23:48:25 +08:00
|
|
|
$(Q)rm -f .tmp_quiet_recordmcount
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2005-09-06 17:47:04 +08:00
|
|
|
# To avoid any implicit rule to kick in, define an empty command.
|
|
|
|
|
scripts/basic/%: scripts_basic ;
|
|
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += outputmakefile
|
2006-05-02 18:33:20 +08: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.
|
2005-04-17 06:20:36 +08:00
|
|
|
outputmakefile:
|
2006-05-02 18:33:20 +08:00
|
|
|
ifneq ($(KBUILD_SRC),)
|
2009-01-10 11:56:13 +08:00
|
|
|
$(Q)ln -fsn $(srctree) source
|
2006-05-02 18:33:20 +08:00
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/mkmakefile \
|
|
|
|
|
$(srctree) $(objtree) $(VERSION) $(PATCHLEVEL)
|
|
|
|
|
endif
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2017-11-08 03:46:13 +08:00
|
|
|
ifeq ($(cc-name),clang)
|
|
|
|
|
ifneq ($(CROSS_COMPILE),)
|
|
|
|
|
CLANG_TARGET := --target=$(notdir $(CROSS_COMPILE:%-=%))
|
|
|
|
|
GCC_TOOLCHAIN := $(realpath $(dir $(shell which $(LD)))/..)
|
|
|
|
|
endif
|
|
|
|
|
ifneq ($(GCC_TOOLCHAIN),)
|
|
|
|
|
CLANG_GCC_TC := --gcc-toolchain=$(GCC_TOOLCHAIN)
|
|
|
|
|
endif
|
|
|
|
|
KBUILD_CFLAGS += $(CLANG_TARGET) $(CLANG_GCC_TC)
|
|
|
|
|
KBUILD_AFLAGS += $(CLANG_TARGET) $(CLANG_GCC_TC)
|
2018-03-20 05:12:53 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-option, -no-integrated-as)
|
|
|
|
|
KBUILD_AFLAGS += $(call cc-option, -no-integrated-as)
|
2017-11-08 03:46:13 +08:00
|
|
|
endif
|
|
|
|
|
|
2018-02-06 16:46:13 +08:00
|
|
|
RETPOLINE_CFLAGS_GCC := -mindirect-branch=thunk-extern -mindirect-branch-register
|
|
|
|
|
RETPOLINE_CFLAGS_CLANG := -mretpoline-external-thunk
|
|
|
|
|
RETPOLINE_CFLAGS := $(call cc-option,$(RETPOLINE_CFLAGS_GCC),$(call cc-option,$(RETPOLINE_CFLAGS_CLANG)))
|
|
|
|
|
export RETPOLINE_CFLAGS
|
|
|
|
|
|
2018-05-16 13:51:36 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fno-PIE)
|
|
|
|
|
KBUILD_AFLAGS += $(call cc-option,-fno-PIE)
|
|
|
|
|
|
2018-01-17 18:42:07 +08:00
|
|
|
# check for 'asm goto'
|
|
|
|
|
ifeq ($(call shell-cached,$(CONFIG_SHELL) $(srctree)/scripts/gcc-goto.sh $(CC) $(KBUILD_CFLAGS)), y)
|
|
|
|
|
CC_HAVE_ASM_GOTO := 1
|
|
|
|
|
KBUILD_CFLAGS += -DCC_HAVE_ASM_GOTO
|
|
|
|
|
KBUILD_AFLAGS += -DCC_HAVE_ASM_GOTO
|
|
|
|
|
endif
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
ifeq ($(config-targets),1)
|
|
|
|
|
# ===========================================================================
|
|
|
|
|
# *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 19:43:36 +08:00
|
|
|
include arch/$(SRCARCH)/Makefile
|
2008-08-25 16:51:27 +08:00
|
|
|
export KBUILD_DEFCONFIG KBUILD_KCONFIG
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-12-14 06:00:45 +08:00
|
|
|
config: scripts_basic outputmakefile FORCE
|
|
|
|
|
$(Q)$(MAKE) $(build)=scripts/kconfig $@
|
|
|
|
|
|
|
|
|
|
%config: scripts_basic outputmakefile FORCE
|
2005-04-17 06:20:36 +08:00
|
|
|
$(Q)$(MAKE) $(build)=scripts/kconfig $@
|
|
|
|
|
|
|
|
|
|
else
|
|
|
|
|
# ===========================================================================
|
|
|
|
|
# Build targets only - this includes vmlinux, arch specific targets, clean
|
|
|
|
|
# targets and others. In general all targets except *config targets.
|
|
|
|
|
|
2017-10-04 11:56:06 +08:00
|
|
|
# If building an external module we do not care about the all: rule
|
|
|
|
|
# but instead _all depend on modules
|
|
|
|
|
PHONY += all
|
|
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
|
|
|
|
_all: all
|
|
|
|
|
else
|
|
|
|
|
_all: modules
|
|
|
|
|
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.
|
|
|
|
|
# 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.
|
|
|
|
|
|
|
|
|
|
ifeq ($(MAKECMDGOALS),modules)
|
|
|
|
|
KBUILD_BUILTIN := $(if $(CONFIG_MODVERSIONS),1)
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
ifneq ($(filter all _all modules,$(MAKECMDGOALS)),)
|
|
|
|
|
KBUILD_MODULES := 1
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
ifeq ($(MAKECMDGOALS),)
|
|
|
|
|
KBUILD_MODULES := 1
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
export KBUILD_MODULES KBUILD_BUILTIN
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
|
|
|
|
# Objects we will link into vmlinux / subdirs we need to visit
|
|
|
|
|
init-y := init/
|
2017-09-16 17:01:16 +08:00
|
|
|
drivers-y := drivers/ sound/ firmware/
|
2005-04-17 06:20:36 +08:00
|
|
|
net-y := net/
|
|
|
|
|
libs-y := lib/
|
|
|
|
|
core-y := usr/
|
2015-09-22 16:47:29 +08:00
|
|
|
virt-y := virt/
|
2005-04-17 06:20:36 +08:00
|
|
|
endif # KBUILD_EXTMOD
|
|
|
|
|
|
|
|
|
|
ifeq ($(dot-config),1)
|
2006-08-08 03:01:36 +08:00
|
|
|
# Read in config
|
|
|
|
|
-include include/config/auto.conf
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-08-08 03:01:36 +08:00
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
2005-04-17 06:20:36 +08:00
|
|
|
# Read in dependencies to all Kconfig* files, make sure to run
|
|
|
|
|
# oldconfig if changes are detected.
|
2006-06-09 13:12:39 +08:00
|
|
|
-include include/config/auto.conf.cmd
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# To avoid any implicit rule to kick in, define an empty command
|
2006-06-09 13:12:51 +08:00
|
|
|
$(KCONFIG_CONFIG) include/config/auto.conf.cmd: ;
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2018-02-13 15:58:20 +08: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).
|
2009-12-07 23:38:33 +08:00
|
|
|
include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
|
2018-03-01 14:34:37 +08:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/Makefile syncconfig
|
2006-06-19 12:09:09 +08:00
|
|
|
else
|
2009-10-18 06:49:24 +08:00
|
|
|
# external modules needs include/generated/autoconf.h and include/config/auto.conf
|
2006-08-08 03:01:36 +08:00
|
|
|
# but do not care if they are up-to-date. Use auto.conf to trigger the test
|
|
|
|
|
PHONY += include/config/auto.conf
|
|
|
|
|
|
|
|
|
|
include/config/auto.conf:
|
2009-10-18 06:49:24 +08:00
|
|
|
$(Q)test -e include/generated/autoconf.h -a -e $@ || ( \
|
2012-07-08 05:04:40 +08: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-08 03:01:36 +08:00
|
|
|
/bin/false)
|
|
|
|
|
|
|
|
|
|
endif # KBUILD_EXTMOD
|
2006-06-09 13:12:39 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
else
|
|
|
|
|
# Dummy target needed, because used as prerequisite
|
2006-06-09 13:12:39 +08:00
|
|
|
include/config/auto.conf: ;
|
2006-08-08 03:01:36 +08:00
|
|
|
endif # $(dot-config)
|
2005-04-17 06:20:36 +08: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
|
2010-06-03 16:54:58 +08:00
|
|
|
# Defaults to vmlinux, but the arch makefile usually adds further targets
|
2005-04-17 06:20:36 +08:00
|
|
|
all: vmlinux
|
|
|
|
|
|
2018-04-27 05:28:07 +08:00
|
|
|
CFLAGS_GCOV := -fprofile-arcs -ftest-coverage \
|
|
|
|
|
$(call cc-option,-fno-tree-loop-im) \
|
|
|
|
|
$(call cc-disable-warning,maybe-uninitialized,)
|
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 17:22:25 +08:00
|
|
|
export CFLAGS_GCOV CFLAGS_KCOV
|
|
|
|
|
|
2015-07-17 00:23:53 +08:00
|
|
|
# The arch Makefile can set ARCH_{CPP,A,C}FLAGS to override the default
|
|
|
|
|
# values of the respective KBUILD_* variables
|
|
|
|
|
ARCH_CPPFLAGS :=
|
|
|
|
|
ARCH_AFLAGS :=
|
|
|
|
|
ARCH_CFLAGS :=
|
2015-03-27 19:43:36 +08:00
|
|
|
include arch/$(SRCARCH)/Makefile
|
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 15:54:12 +08:00
|
|
|
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fno-delete-null-pointer-checks,)
|
2016-10-13 01:23:41 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning,frame-address,)
|
2017-07-13 10:25:47 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, format-truncation)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, format-overflow)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, int-in-bool-context)
|
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 15:54:12 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
|
2017-03-28 09:19:09 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Oz,-Os)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning,maybe-uninitialized,)
|
2005-04-17 06:20:36 +08:00
|
|
|
else
|
2016-04-25 23:35:28 +08:00
|
|
|
ifdef CONFIG_PROFILE_ALL_BRANCHES
|
Kbuild: enable -Wmaybe-uninitialized warning for "make W=1"
Traditionally, we have always had warnings about uninitialized variables
enabled, as this is part of -Wall, and generally a good idea [1], but it
also always produced false positives, mainly because this is a variation
of the halting problem and provably impossible to get right in all cases
[2].
Various people have identified cases that are particularly bad for false
positives, and in commit e74fc973b6e5 ("Turn off -Wmaybe-uninitialized
when building with -Os"), I turned off the warning for any build that
was done with CC_OPTIMIZE_FOR_SIZE. This drastically reduced the number
of false positive warnings in the default build but unfortunately had
the side effect of turning the warning off completely in 'allmodconfig'
builds, which in turn led to a lot of warnings (both actual bugs, and
remaining false positives) to go in unnoticed.
With commit 877417e6ffb9 ("Kbuild: change CC_OPTIMIZE_FOR_SIZE
definition") enabled the warning again for allmodconfig builds in v4.7
and in v4.8-rc1, I had finally managed to address all warnings I get in
an ARM allmodconfig build and most other maybe-uninitialized warnings
for ARM randconfig builds.
However, commit 6e8d666e9253 ("Disable "maybe-uninitialized" warning
globally") was merged at the same time and disabled it completely for
all configurations, because of false-positive warnings on x86 that I had
not addressed until then. This caused a lot of actual bugs to get
merged into mainline, and I sent several dozen patches for these during
the v4.9 development cycle. Most of these are actual bugs, some are for
correct code that is safe because it is only called under external
constraints that make it impossible to run into the case that gcc sees,
and in a few cases gcc is just stupid and finds something that can
obviously never happen.
I have now done a few thousand randconfig builds on x86 and collected
all patches that I needed to address every single warning I got (I can
provide the combined patch for the other warnings if anyone is
interested), so I hope we can get the warning back and let people catch
the actual bugs earlier.
This reverts the change to disable the warning completely and for now
brings it back at the "make W=1" level, so we can get it merged into
mainline without introducing false positives. A follow-up patch enables
it on all levels unless some configuration option turns it off because
of false-positives.
Link: https://rusty.ozlabs.org/?p=232 [1]
Link: https://gcc.gnu.org/wiki/Better_Uninitialized_Warnings [2]
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-11-11 00:44:44 +08:00
|
|
|
KBUILD_CFLAGS += -O2 $(call cc-disable-warning,maybe-uninitialized,)
|
2016-04-25 23:35:28 +08:00
|
|
|
else
|
|
|
|
|
KBUILD_CFLAGS += -O2
|
|
|
|
|
endif
|
2005-04-17 06:20:36 +08:00
|
|
|
endif
|
|
|
|
|
|
Kbuild: enable -Wmaybe-uninitialized warning for "make W=1"
Traditionally, we have always had warnings about uninitialized variables
enabled, as this is part of -Wall, and generally a good idea [1], but it
also always produced false positives, mainly because this is a variation
of the halting problem and provably impossible to get right in all cases
[2].
Various people have identified cases that are particularly bad for false
positives, and in commit e74fc973b6e5 ("Turn off -Wmaybe-uninitialized
when building with -Os"), I turned off the warning for any build that
was done with CC_OPTIMIZE_FOR_SIZE. This drastically reduced the number
of false positive warnings in the default build but unfortunately had
the side effect of turning the warning off completely in 'allmodconfig'
builds, which in turn led to a lot of warnings (both actual bugs, and
remaining false positives) to go in unnoticed.
With commit 877417e6ffb9 ("Kbuild: change CC_OPTIMIZE_FOR_SIZE
definition") enabled the warning again for allmodconfig builds in v4.7
and in v4.8-rc1, I had finally managed to address all warnings I get in
an ARM allmodconfig build and most other maybe-uninitialized warnings
for ARM randconfig builds.
However, commit 6e8d666e9253 ("Disable "maybe-uninitialized" warning
globally") was merged at the same time and disabled it completely for
all configurations, because of false-positive warnings on x86 that I had
not addressed until then. This caused a lot of actual bugs to get
merged into mainline, and I sent several dozen patches for these during
the v4.9 development cycle. Most of these are actual bugs, some are for
correct code that is safe because it is only called under external
constraints that make it impossible to run into the case that gcc sees,
and in a few cases gcc is just stupid and finds something that can
obviously never happen.
I have now done a few thousand randconfig builds on x86 and collected
all patches that I needed to address every single warning I got (I can
provide the combined patch for the other warnings if anyone is
interested), so I hope we can get the warning back and let people catch
the actual bugs earlier.
This reverts the change to disable the warning completely and for now
brings it back at the "make W=1" level, so we can get it merged into
mainline without introducing false positives. A follow-up patch enables
it on all levels unless some configuration option turns it off because
of false-positives.
Link: https://rusty.ozlabs.org/?p=232 [1]
Link: https://gcc.gnu.org/wiki/Better_Uninitialized_Warnings [2]
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-11-11 00:44:44 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-ifversion, -lt, 0409, \
|
|
|
|
|
$(call cc-disable-warning,maybe-uninitialized,))
|
|
|
|
|
|
./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-07 07:08:43 +08:00
|
|
|
# Tell gcc to never replace conditional load with a non-conditional one
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,--param=allow-store-data-races=0)
|
|
|
|
|
|
2017-11-18 07:30:50 +08:00
|
|
|
include scripts/Makefile.kcov
|
2016-05-24 06:09:38 +08:00
|
|
|
include scripts/Makefile.gcc-plugins
|
|
|
|
|
|
2012-03-29 02:51:18 +08: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-05 07:29:08 +08:00
|
|
|
ifneq ($(CONFIG_FRAME_WARN),0)
|
2008-02-22 22:15:03 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Wframe-larger-than=${CONFIG_FRAME_WARN})
|
|
|
|
|
endif
|
|
|
|
|
|
2016-07-27 06:21:17 +08:00
|
|
|
# This selects the stack protector compiler flag. Testing it is delayed
|
|
|
|
|
# until after .config has been reprocessed, in the prepare-compiler-check
|
|
|
|
|
# target.
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
ifdef CONFIG_CC_STACKPROTECTOR_AUTO
|
|
|
|
|
stackp-flag := $(call cc-option,-fstack-protector-strong,$(call cc-option,-fstack-protector))
|
|
|
|
|
stackp-name := AUTO
|
|
|
|
|
else
|
stackprotector: Introduce CONFIG_CC_STACKPROTECTOR_STRONG
This changes the stack protector config option into a choice of
"None", "Regular", and "Strong":
CONFIG_CC_STACKPROTECTOR_NONE
CONFIG_CC_STACKPROTECTOR_REGULAR
CONFIG_CC_STACKPROTECTOR_STRONG
"Regular" means the old CONFIG_CC_STACKPROTECTOR=y option.
"Strong" is a new mode introduced by this patch. With "Strong" the
kernel is built with -fstack-protector-strong (available in
gcc 4.9 and later). This option increases the coverage of the stack
protector without the heavy performance hit of -fstack-protector-all.
For reference, the stack protector options available in gcc are:
-fstack-protector-all:
Adds the stack-canary saving prefix and stack-canary checking
suffix to _all_ function entry and exit. Results in substantial
use of stack space for saving the canary for deep stack users
(e.g. historically xfs), and measurable (though shockingly still
low) performance hit due to all the saving/checking. Really not
suitable for sane systems, and was entirely removed as an option
from the kernel many years ago.
-fstack-protector:
Adds the canary save/check to functions that define an 8
(--param=ssp-buffer-size=N, N=8 by default) or more byte local
char array. Traditionally, stack overflows happened with
string-based manipulations, so this was a way to find those
functions. Very few total functions actually get the canary; no
measurable performance or size overhead.
-fstack-protector-strong
Adds the canary for a wider set of functions, since it's not
just those with strings that have ultimately been vulnerable to
stack-busting. With this superset, more functions end up with a
canary, but it still remains small compared to all functions
with only a small change in performance. Based on the original
design document, a function gets the canary when it contains any
of:
- local variable's address used as part of the right hand side
of an assignment or function argument
- local variable is an array (or union containing an array),
regardless of array type or length
- uses register local variables
https://docs.google.com/a/google.com/document/d/1xXBH6rRZue4f296vGt9YQcuLVQHeE516stHwt8M9xyU
Find below a comparison of "size" and "objdump" output when built with
gcc-4.9 in three configurations:
- defconfig
11430641 kernel text size
36110 function bodies
- defconfig + CONFIG_CC_STACKPROTECTOR_REGULAR
11468490 kernel text size (+0.33%)
1015 of 36110 functions are stack-protected (2.81%)
- defconfig + CONFIG_CC_STACKPROTECTOR_STRONG via this patch
11692790 kernel text size (+2.24%)
7401 of 36110 functions are stack-protected (20.5%)
With -strong, ARM's compressed boot code now triggers stack
protection, so a static guard was added. Since this is only used
during decompression and was never used before, the exposure
here is very small. Once it switches to the full kernel, the
stack guard is back to normal.
Chrome OS has been using -fstack-protector-strong for its kernel
builds for the last 8 months with no problems.
Signed-off-by: Kees Cook <keescook@chromium.org>
Cc: Arjan van de Ven <arjan@linux.intel.com>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Mundt <lethal@linux-sh.org>
Cc: James Hogan <james.hogan@imgtec.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Shawn Guo <shawn.guo@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-mips@linux-mips.org
Cc: linux-arch@vger.kernel.org
Link: http://lkml.kernel.org/r/1387481759-14535-3-git-send-email-keescook@chromium.org
[ Improved the changelog and descriptions some more. ]
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2013-12-20 03:35:59 +08:00
|
|
|
ifdef CONFIG_CC_STACKPROTECTOR_REGULAR
|
2013-12-20 03:35:58 +08:00
|
|
|
stackp-flag := -fstack-protector
|
2016-07-27 06:21:17 +08:00
|
|
|
stackp-name := REGULAR
|
2014-02-26 07:01:48 +08:00
|
|
|
else
|
|
|
|
|
ifdef CONFIG_CC_STACKPROTECTOR_STRONG
|
stackprotector: Introduce CONFIG_CC_STACKPROTECTOR_STRONG
This changes the stack protector config option into a choice of
"None", "Regular", and "Strong":
CONFIG_CC_STACKPROTECTOR_NONE
CONFIG_CC_STACKPROTECTOR_REGULAR
CONFIG_CC_STACKPROTECTOR_STRONG
"Regular" means the old CONFIG_CC_STACKPROTECTOR=y option.
"Strong" is a new mode introduced by this patch. With "Strong" the
kernel is built with -fstack-protector-strong (available in
gcc 4.9 and later). This option increases the coverage of the stack
protector without the heavy performance hit of -fstack-protector-all.
For reference, the stack protector options available in gcc are:
-fstack-protector-all:
Adds the stack-canary saving prefix and stack-canary checking
suffix to _all_ function entry and exit. Results in substantial
use of stack space for saving the canary for deep stack users
(e.g. historically xfs), and measurable (though shockingly still
low) performance hit due to all the saving/checking. Really not
suitable for sane systems, and was entirely removed as an option
from the kernel many years ago.
-fstack-protector:
Adds the canary save/check to functions that define an 8
(--param=ssp-buffer-size=N, N=8 by default) or more byte local
char array. Traditionally, stack overflows happened with
string-based manipulations, so this was a way to find those
functions. Very few total functions actually get the canary; no
measurable performance or size overhead.
-fstack-protector-strong
Adds the canary for a wider set of functions, since it's not
just those with strings that have ultimately been vulnerable to
stack-busting. With this superset, more functions end up with a
canary, but it still remains small compared to all functions
with only a small change in performance. Based on the original
design document, a function gets the canary when it contains any
of:
- local variable's address used as part of the right hand side
of an assignment or function argument
- local variable is an array (or union containing an array),
regardless of array type or length
- uses register local variables
https://docs.google.com/a/google.com/document/d/1xXBH6rRZue4f296vGt9YQcuLVQHeE516stHwt8M9xyU
Find below a comparison of "size" and "objdump" output when built with
gcc-4.9 in three configurations:
- defconfig
11430641 kernel text size
36110 function bodies
- defconfig + CONFIG_CC_STACKPROTECTOR_REGULAR
11468490 kernel text size (+0.33%)
1015 of 36110 functions are stack-protected (2.81%)
- defconfig + CONFIG_CC_STACKPROTECTOR_STRONG via this patch
11692790 kernel text size (+2.24%)
7401 of 36110 functions are stack-protected (20.5%)
With -strong, ARM's compressed boot code now triggers stack
protection, so a static guard was added. Since this is only used
during decompression and was never used before, the exposure
here is very small. Once it switches to the full kernel, the
stack guard is back to normal.
Chrome OS has been using -fstack-protector-strong for its kernel
builds for the last 8 months with no problems.
Signed-off-by: Kees Cook <keescook@chromium.org>
Cc: Arjan van de Ven <arjan@linux.intel.com>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Mundt <lethal@linux-sh.org>
Cc: James Hogan <james.hogan@imgtec.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Shawn Guo <shawn.guo@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-mips@linux-mips.org
Cc: linux-arch@vger.kernel.org
Link: http://lkml.kernel.org/r/1387481759-14535-3-git-send-email-keescook@chromium.org
[ Improved the changelog and descriptions some more. ]
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2013-12-20 03:35:59 +08:00
|
|
|
stackp-flag := -fstack-protector-strong
|
2016-07-27 06:21:17 +08:00
|
|
|
stackp-name := STRONG
|
2013-12-20 03:35:58 +08:00
|
|
|
else
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
# If either there is no stack protector for this architecture or
|
|
|
|
|
# CONFIG_CC_STACKPROTECTOR_NONE is selected, we're done, and $(stackp-name)
|
|
|
|
|
# is empty, skipping all remaining stack protector tests.
|
|
|
|
|
#
|
2013-12-20 03:35:58 +08:00
|
|
|
# Force off for distro compilers that enable stack protector by default.
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-option, -fno-stack-protector)
|
|
|
|
|
endif
|
2009-02-09 21:17:39 +08:00
|
|
|
endif
|
2014-02-26 07:01:48 +08:00
|
|
|
endif
|
2016-07-27 06:21:17 +08:00
|
|
|
# Find arch-specific stack protector compiler sanity-checking script.
|
2018-02-07 07:37:41 +08:00
|
|
|
ifdef stackp-name
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
ifneq ($(stackp-flag),)
|
2016-07-27 05:26:20 +08:00
|
|
|
stackp-path := $(srctree)/scripts/gcc-$(SRCARCH)_$(BITS)-has-stack-protector.sh
|
|
|
|
|
stackp-check := $(wildcard $(stackp-path))
|
2018-02-07 07:37:38 +08:00
|
|
|
# If the wildcard test matches a test script, run it to check functionality.
|
|
|
|
|
ifdef stackp-check
|
|
|
|
|
ifneq ($(shell $(CONFIG_SHELL) $(stackp-check) $(CC) $(KBUILD_CPPFLAGS) $(biarch)),y)
|
|
|
|
|
stackp-broken := y
|
|
|
|
|
endif
|
|
|
|
|
endif
|
2018-02-07 07:37:41 +08:00
|
|
|
ifndef stackp-broken
|
|
|
|
|
# If the stack protector is functional, enable code that depends on it.
|
|
|
|
|
KBUILD_CPPFLAGS += -DCONFIG_CC_STACKPROTECTOR
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
# Either we've already detected the flag (for AUTO) or we'll fail the
|
|
|
|
|
# build in the prepare-compiler-check rule (for specific flag).
|
|
|
|
|
KBUILD_CFLAGS += $(stackp-flag)
|
|
|
|
|
else
|
|
|
|
|
# We have to make sure stack protector is unconditionally disabled if
|
|
|
|
|
# the compiler is broken (in case we're going to continue the build in
|
|
|
|
|
# AUTO mode).
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option, -fno-stack-protector)
|
2018-02-07 07:37:41 +08:00
|
|
|
endif
|
2016-07-27 06:21:17 +08:00
|
|
|
endif
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
endif
|
2008-02-14 05:43:28 +08:00
|
|
|
|
2017-11-27 20:15:13 +08:00
|
|
|
ifeq ($(cc-name),clang)
|
|
|
|
|
KBUILD_CPPFLAGS += $(call cc-option,-Qunused-arguments,)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, format-invalid-specifier)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, gnu)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, address-of-packed-member)
|
|
|
|
|
# Quiet clang warning: comparison of unsigned expression < 0 is always false
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, tautological-compare)
|
|
|
|
|
# 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
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option, -mno-global-merge,)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option, -fcatch-undefined-behavior)
|
|
|
|
|
else
|
|
|
|
|
|
|
|
|
|
# These warnings generated too much noise in a regular build.
|
|
|
|
|
# Use make W=1 to enable them (see scripts/Makefile.extrawarn)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, unused-but-set-variable)
|
|
|
|
|
endif
|
|
|
|
|
|
2018-02-07 07:46:51 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, unused-const-variable)
|
2005-04-17 06:20:36 +08:00
|
|
|
ifdef CONFIG_FRAME_POINTER
|
2007-10-15 04:21:35 +08:00
|
|
|
KBUILD_CFLAGS += -fno-omit-frame-pointer -fno-optimize-sibling-calls
|
2005-04-17 06:20:36 +08:00
|
|
|
else
|
2010-08-11 02:20:53 +08: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-15 04:21:35 +08:00
|
|
|
KBUILD_CFLAGS += -fomit-frame-pointer
|
2005-04-17 06:20:36 +08:00
|
|
|
endif
|
2010-08-11 02:20:53 +08:00
|
|
|
endif
|
2005-04-17 06:20:36 +08:00
|
|
|
|
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-27 05:52:01 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-option, -fno-var-tracking-assignments)
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
ifdef CONFIG_DEBUG_INFO
|
2014-07-31 02:50:18 +08:00
|
|
|
ifdef CONFIG_DEBUG_INFO_SPLIT
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option, -gsplit-dwarf, -g)
|
|
|
|
|
else
|
2007-10-15 04:21:35 +08:00
|
|
|
KBUILD_CFLAGS += -g
|
2014-07-31 02:50:18 +08:00
|
|
|
endif
|
2014-02-15 07:19:17 +08:00
|
|
|
KBUILD_AFLAGS += -Wa,-gdwarf-2
|
2005-04-17 06:20:36 +08:00
|
|
|
endif
|
2014-07-31 02:50:19 +08:00
|
|
|
ifdef CONFIG_DEBUG_INFO_DWARF4
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option, -gdwarf-4,)
|
|
|
|
|
endif
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2010-07-14 21:43:52 +08:00
|
|
|
ifdef CONFIG_DEBUG_INFO_REDUCED
|
2013-02-08 05:58:40 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-option, -femit-struct-debug-baseonly) \
|
|
|
|
|
$(call cc-option,-fno-var-tracking)
|
2010-07-14 21:43:52 +08:00
|
|
|
endif
|
|
|
|
|
|
2008-10-07 07:06:12 +08:00
|
|
|
ifdef CONFIG_FUNCTION_TRACER
|
2015-01-09 20:06:33 +08:00
|
|
|
ifndef CC_FLAGS_FTRACE
|
|
|
|
|
CC_FLAGS_FTRACE := -pg
|
|
|
|
|
endif
|
|
|
|
|
export CC_FLAGS_FTRACE
|
2011-02-10 02:15:59 +08:00
|
|
|
ifdef CONFIG_HAVE_FENTRY
|
|
|
|
|
CC_USING_FENTRY := $(call cc-option, -mfentry -DCC_USING_FENTRY)
|
|
|
|
|
endif
|
2015-01-09 20:06:33 +08:00
|
|
|
KBUILD_CFLAGS += $(CC_FLAGS_FTRACE) $(CC_USING_FENTRY)
|
2011-02-10 02:15:59 +08:00
|
|
|
KBUILD_AFLAGS += $(CC_USING_FENTRY)
|
2010-10-14 05:12:30 +08:00
|
|
|
ifdef CONFIG_DYNAMIC_FTRACE
|
2010-10-15 11:32:44 +08:00
|
|
|
ifdef CONFIG_HAVE_C_RECORDMCOUNT
|
2010-10-14 05:12:30 +08:00
|
|
|
BUILD_C_RECORDMCOUNT := y
|
|
|
|
|
export BUILD_C_RECORDMCOUNT
|
|
|
|
|
endif
|
|
|
|
|
endif
|
2008-05-13 03:20:42 +08:00
|
|
|
endif
|
|
|
|
|
|
2008-01-22 04:31:44 +08: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 14:17:26 +08:00
|
|
|
ifdef CONFIG_LD_DEAD_CODE_DATA_ELIMINATION
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-ffunction-sections,)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fdata-sections,)
|
|
|
|
|
endif
|
|
|
|
|
|
2005-05-01 07:51:42 +08:00
|
|
|
# arch Makefile may override CC so keep this after arch Makefile is included
|
2017-10-17 01:12:46 +08:00
|
|
|
NOSTDINC_FLAGS += -nostdinc -isystem $(call shell-cached,$(CC) -print-file-name=include)
|
2005-05-01 07:51:42 +08:00
|
|
|
CHECKFLAGS += $(NOSTDINC_FLAGS)
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# warn about C99 declaration after statement
|
2007-10-15 04:21:35 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Wdeclaration-after-statement,)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-06-25 06:07:55 +08:00
|
|
|
# disable pointer signed / unsigned warnings in gcc 4.0
|
2011-05-02 18:51:15 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-disable-warning, pointer-sign)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-04-09 19:34:34 +08:00
|
|
|
# disable invalid "can't wrap" optimizations for signed / pointers
|
2009-07-13 02:25:04 +08:00
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fno-strict-overflow)
|
2009-03-20 06:53:19 +08: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 08:18:24 +08: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 09:34:43 +08:00
|
|
|
# Make sure -fstack-check isn't enabled (like gentoo apparently did)
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fno-stack-check,)
|
|
|
|
|
|
2009-09-19 03:49:37 +08:00
|
|
|
# conserve stack if available
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fconserve-stack)
|
|
|
|
|
|
2013-09-14 05:51:40 +08:00
|
|
|
# disallow errors like 'EXPORT_GPL(foo);' with missing header
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Werror=implicit-int)
|
|
|
|
|
|
|
|
|
|
# require functions to have arguments in prototypes, not empty 'int foo()'
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Werror=strict-prototypes)
|
|
|
|
|
|
2013-12-24 05:56:06 +08:00
|
|
|
# Prohibit date/time macros, which would make the build non-deterministic
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Werror=date-time)
|
|
|
|
|
|
2016-03-08 16:29:09 +08:00
|
|
|
# enforce correct pointer usage
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Werror=incompatible-pointer-types)
|
|
|
|
|
|
2017-03-21 08:14:11 +08:00
|
|
|
# Require designated initializers for all marked structures
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-Werror=designated-init)
|
|
|
|
|
|
2018-03-30 12:15:26 +08:00
|
|
|
# change __FILE__ to the relative path from the srctree
|
|
|
|
|
KBUILD_CFLAGS += $(call cc-option,-fmacro-prefix-map=$(srctree)/=)
|
|
|
|
|
|
2011-04-20 19:45:30 +08:00
|
|
|
# use the deterministic mode of AR if available
|
|
|
|
|
KBUILD_ARFLAGS := $(call ar-option,D)
|
|
|
|
|
|
2015-03-27 19:43:36 +08:00
|
|
|
include scripts/Makefile.kasan
|
|
|
|
|
include scripts/Makefile.extrawarn
|
2016-01-21 07:00:55 +08:00
|
|
|
include scripts/Makefile.ubsan
|
2014-04-14 17:27:10 +08:00
|
|
|
|
2015-07-01 23:19:30 +08:00
|
|
|
# Add any arch overrides and user supplied CPPFLAGS, AFLAGS and CFLAGS as the
|
|
|
|
|
# last assignments
|
|
|
|
|
KBUILD_CPPFLAGS += $(ARCH_CPPFLAGS) $(KCPPFLAGS)
|
|
|
|
|
KBUILD_AFLAGS += $(ARCH_AFLAGS) $(KAFLAGS)
|
|
|
|
|
KBUILD_CFLAGS += $(ARCH_CFLAGS) $(KCFLAGS)
|
2007-10-16 04:03:58 +08:00
|
|
|
|
2007-07-19 16:48:40 +08:00
|
|
|
# Use --build-id when available.
|
2018-02-23 12:56:52 +08:00
|
|
|
LDFLAGS_BUILD_ID := $(call ld-option, --build-id)
|
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 23:33:09 +08:00
|
|
|
KBUILD_LDFLAGS_MODULE += $(LDFLAGS_BUILD_ID)
|
2007-07-19 16:48:40 +08:00
|
|
|
LDFLAGS_vmlinux += $(LDFLAGS_BUILD_ID)
|
|
|
|
|
|
kbuild: allow archs to select link dead code/data elimination
Introduce LD_DEAD_CODE_DATA_ELIMINATION option for architectures to
select to build with -ffunction-sections, -fdata-sections, and link
with --gc-sections. It requires some work (documented) to ensure all
unreferenced entrypoints are live, and requires toolchain and build
verification, so it is made a per-arch option for now.
On a random powerpc64le build, this yelds a significant size saving,
it boots and runs fine, but there is a lot I haven't tested as yet, so
these savings may be reduced if there are bugs in the link.
text data bss dec filename
11169741 1180744 1923176 14273661 vmlinux
10445269 1004127 1919707 13369103 vmlinux.dce
~700K text, ~170K data, 6% removed from kernel image size.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Signed-off-by: Michal Marek <mmarek@suse.com>
2016-08-24 20:29:20 +08:00
|
|
|
ifdef CONFIG_LD_DEAD_CODE_DATA_ELIMINATION
|
|
|
|
|
LDFLAGS_vmlinux += $(call ld-option, --gc-sections,)
|
|
|
|
|
endif
|
|
|
|
|
|
2009-03-05 03:59:07 +08:00
|
|
|
ifeq ($(CONFIG_STRIP_ASM_SYMS),y)
|
2009-09-17 04:36:55 +08:00
|
|
|
LDFLAGS_vmlinux += $(call ld-option, -X,)
|
2009-03-05 03:59:07 +08:00
|
|
|
endif
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# Default kernel image to build when no specific target is given.
|
2006-06-25 06:07:55 +08:00
|
|
|
# KBUILD_IMAGE may be overruled on the command line or
|
2005-04-17 06:20:36 +08: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-02 07:56:28 +08: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-17 06:20:36 +08: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-25 06:07:55 +08:00
|
|
|
# makefile but the argument can be passed to make if needed.
|
2005-04-17 06:20:36 +08:00
|
|
|
#
|
|
|
|
|
|
2006-01-16 19:46:07 +08:00
|
|
|
MODLIB = $(INSTALL_MOD_PATH)/lib/modules/$(KERNELRELEASE)
|
2005-04-17 06:20:36 +08:00
|
|
|
export MODLIB
|
|
|
|
|
|
2006-06-22 08:53:09 +08:00
|
|
|
#
|
2014-04-28 15:32:43 +08: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-15 04:38:20 +08:00
|
|
|
|
2006-06-22 08:53:09 +08:00
|
|
|
ifdef INSTALL_MOD_STRIP
|
|
|
|
|
ifeq ($(INSTALL_MOD_STRIP),1)
|
2009-01-15 04:38:20 +08:00
|
|
|
mod_strip_cmd = $(STRIP) --strip-debug
|
2006-06-22 08:53:09 +08:00
|
|
|
else
|
2009-01-15 04:38:20 +08:00
|
|
|
mod_strip_cmd = $(STRIP) $(INSTALL_MOD_STRIP)
|
2006-06-22 08:53:09 +08:00
|
|
|
endif # INSTALL_MOD_STRIP=1
|
|
|
|
|
else
|
2009-01-15 04:38:20 +08:00
|
|
|
mod_strip_cmd = true
|
2006-06-22 08:53:09 +08:00
|
|
|
endif # INSTALL_MOD_STRIP
|
|
|
|
|
export mod_strip_cmd
|
|
|
|
|
|
2014-08-27 19:01:56 +08: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
|
2015-07-08 02:26:07 +08:00
|
|
|
mod_compress_cmd = gzip -n -f
|
2014-08-27 19:01:56 +08:00
|
|
|
endif # CONFIG_MODULE_COMPRESS_GZIP
|
|
|
|
|
ifdef CONFIG_MODULE_COMPRESS_XZ
|
2015-07-08 02:26:07 +08:00
|
|
|
mod_compress_cmd = xz -f
|
2014-08-27 19:01:56 +08:00
|
|
|
endif # CONFIG_MODULE_COMPRESS_XZ
|
|
|
|
|
endif # CONFIG_MODULE_COMPRESS
|
|
|
|
|
export mod_compress_cmd
|
|
|
|
|
|
2013-11-13 07:11:44 +08:00
|
|
|
# Select initial ramdisk compression format, default is gzip(1).
|
|
|
|
|
# This shall be used by the dracut(8) tool while creating an initramfs image.
|
|
|
|
|
#
|
2013-12-19 09:08:57 +08:00
|
|
|
INITRD_COMPRESS-y := gzip
|
|
|
|
|
INITRD_COMPRESS-$(CONFIG_RD_BZIP2) := bzip2
|
|
|
|
|
INITRD_COMPRESS-$(CONFIG_RD_LZMA) := lzma
|
|
|
|
|
INITRD_COMPRESS-$(CONFIG_RD_XZ) := xz
|
|
|
|
|
INITRD_COMPRESS-$(CONFIG_RD_LZO) := lzo
|
|
|
|
|
INITRD_COMPRESS-$(CONFIG_RD_LZ4) := lz4
|
2013-12-21 08:52:45 +08:00
|
|
|
# do not export INITRD_COMPRESS, since we didn't actually
|
|
|
|
|
# choose a sane default compression above.
|
|
|
|
|
# export INITRD_COMPRESS := $(INITRD_COMPRESS-y)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2013-01-25 11:11:31 +08:00
|
|
|
ifdef CONFIG_MODULE_SIG_ALL
|
2015-08-14 23:17:16 +08: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 09:23:15 +08:00
|
|
|
else
|
|
|
|
|
mod_sign_cmd = true
|
|
|
|
|
endif
|
|
|
|
|
export mod_sign_cmd
|
|
|
|
|
|
2017-02-16 02:21:17 +08:00
|
|
|
ifdef CONFIG_STACK_VALIDATION
|
|
|
|
|
has_libelf := $(call try-run,\
|
|
|
|
|
echo "int main() {}" | $(HOSTCC) -xc -o /dev/null -lelf -,1,0)
|
|
|
|
|
ifeq ($(has_libelf),1)
|
|
|
|
|
objtool_target := tools/objtool FORCE
|
|
|
|
|
else
|
2017-10-14 04:02:00 +08:00
|
|
|
ifdef CONFIG_UNWINDER_ORC
|
|
|
|
|
$(error "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel")
|
2017-10-04 09:10:36 +08:00
|
|
|
else
|
|
|
|
|
$(warning "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel")
|
|
|
|
|
endif
|
2017-02-16 02:21:17 +08:00
|
|
|
SKIP_STACK_VALIDATION := 1
|
|
|
|
|
export SKIP_STACK_VALIDATION
|
|
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
2012-10-19 09:23:15 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
2015-08-14 22:20:41 +08:00
|
|
|
core-y += kernel/ certs/ mm/ fs/ ipc/ security/ crypto/ block/
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
vmlinux-dirs := $(patsubst %/,%,$(filter %/, $(init-y) $(init-m) \
|
|
|
|
|
$(core-y) $(core-m) $(drivers-y) $(drivers-m) \
|
2015-09-22 16:47:29 +08:00
|
|
|
$(net-y) $(net-m) $(libs-y) $(libs-m) $(virt-y)))
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
vmlinux-alldirs := $(sort $(vmlinux-dirs) $(patsubst %/,%,$(filter %/, \
|
2015-09-22 16:47:29 +08:00
|
|
|
$(init-) $(core-) $(drivers-) $(net-) $(libs-) $(virt-))))
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2018-02-10 22:25:04 +08:00
|
|
|
init-y := $(patsubst %/, %/built-in.a, $(init-y))
|
|
|
|
|
core-y := $(patsubst %/, %/built-in.a, $(core-y))
|
|
|
|
|
drivers-y := $(patsubst %/, %/built-in.a, $(drivers-y))
|
|
|
|
|
net-y := $(patsubst %/, %/built-in.a, $(net-y))
|
2005-04-17 06:20:36 +08:00
|
|
|
libs-y1 := $(patsubst %/, %/lib.a, $(libs-y))
|
2018-02-10 22:25:04 +08:00
|
|
|
libs-y2 := $(patsubst %/, %/built-in.a, $(filter-out %.a, $(libs-y)))
|
|
|
|
|
virt-y := $(patsubst %/, %/built-in.a, $(virt-y))
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2012-05-05 16:18:41 +08:00
|
|
|
# Externally visible symbols (used by link-vmlinux.sh)
|
2012-05-05 16:18:40 +08:00
|
|
|
export KBUILD_VMLINUX_INIT := $(head-y) $(init-y)
|
2017-06-19 23:52:05 +08:00
|
|
|
export KBUILD_VMLINUX_MAIN := $(core-y) $(libs-y2) $(drivers-y) $(net-y) $(virt-y)
|
|
|
|
|
export KBUILD_VMLINUX_LIBS := $(libs-y1)
|
2012-05-05 16:18:40 +08:00
|
|
|
export KBUILD_LDS := arch/$(SRCARCH)/kernel/vmlinux.lds
|
2012-05-05 16:18:41 +08:00
|
|
|
export LDFLAGS_vmlinux
|
2017-08-02 10:31:06 +08:00
|
|
|
# used by scripts/package/Makefile
|
2015-09-22 16:47:29 +08:00
|
|
|
export KBUILD_ALLDIRS := $(sort $(filter-out arch/%,$(vmlinux-alldirs)) arch Documentation include samples scripts tools)
|
2008-12-16 19:30:08 +08:00
|
|
|
|
2017-06-19 23:52:05 +08:00
|
|
|
vmlinux-deps := $(KBUILD_LDS) $(KBUILD_VMLINUX_INIT) $(KBUILD_VMLINUX_MAIN) $(KBUILD_VMLINUX_LIBS)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2018-03-16 15:37:15 +08:00
|
|
|
# Recurse until adjust_autoksyms.sh is satisfied
|
|
|
|
|
PHONY += autoksyms_recursive
|
|
|
|
|
autoksyms_recursive: $(vmlinux-deps)
|
2016-04-23 03:25:00 +08:00
|
|
|
ifdef CONFIG_TRIM_UNUSED_KSYMS
|
2016-04-25 23:55:08 +08:00
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/adjust_autoksyms.sh \
|
2016-12-03 04:11:50 +08:00
|
|
|
"$(MAKE) -f $(srctree)/Makefile vmlinux"
|
2016-04-23 03:25:00 +08:00
|
|
|
endif
|
2016-01-27 10:50:18 +08:00
|
|
|
|
2018-03-16 15:37:13 +08: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)
|
|
|
|
|
ifdef CONFIG_TRIM_UNUSED_KSYMS
|
|
|
|
|
KBUILD_MODULES := 1
|
|
|
|
|
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 15:37:12 +08:00
|
|
|
autoksyms_h := $(if $(CONFIG_TRIM_UNUSED_KSYMS), include/generated/autoksyms.h)
|
|
|
|
|
|
|
|
|
|
$(autoksyms_h):
|
|
|
|
|
$(Q)mkdir -p $(dir $@)
|
|
|
|
|
$(Q)touch $@
|
2016-01-27 10:50:18 +08:00
|
|
|
|
2016-08-24 20:29:21 +08:00
|
|
|
ARCH_POSTLINK := $(wildcard $(srctree)/arch/$(SRCARCH)/Makefile.postlink)
|
|
|
|
|
|
|
|
|
|
# Final link of vmlinux with optional arch pass after final link
|
2017-08-02 10:31:06 +08:00
|
|
|
cmd_link-vmlinux = \
|
|
|
|
|
$(CONFIG_SHELL) $< $(LD) $(LDFLAGS) $(LDFLAGS_vmlinux) ; \
|
2016-08-24 20:29:21 +08:00
|
|
|
$(if $(ARCH_POSTLINK), $(MAKE) -f $(ARCH_POSTLINK) $@, true)
|
2016-04-23 03:25:00 +08:00
|
|
|
|
2018-03-16 15:37:15 +08:00
|
|
|
vmlinux: scripts/link-vmlinux.sh autoksyms_recursive $(vmlinux-deps) FORCE
|
|
|
|
|
ifdef CONFIG_HEADERS_CHECK
|
|
|
|
|
$(Q)$(MAKE) -f $(srctree)/Makefile headers_check
|
|
|
|
|
endif
|
|
|
|
|
ifdef CONFIG_GDB_SCRIPTS
|
|
|
|
|
$(Q)ln -fsn $(abspath $(srctree)/scripts/gdb/vmlinux-gdb.py)
|
|
|
|
|
endif
|
2012-05-05 16:18:41 +08:00
|
|
|
+$(call if_changed,link-vmlinux)
|
2007-07-17 16:54:06 +08:00
|
|
|
|
2016-02-29 11:00:00 +08:00
|
|
|
# Build samples along the rest of the kernel
|
|
|
|
|
ifdef CONFIG_SAMPLES
|
|
|
|
|
vmlinux-dirs += samples
|
|
|
|
|
endif
|
|
|
|
|
|
2014-04-28 15:26:18 +08:00
|
|
|
# The actual objects are generated when descending,
|
2005-04-17 06:20:36 +08:00
|
|
|
# make sure no implicit rule kicks in
|
2012-05-05 16:18:41 +08:00
|
|
|
$(sort $(vmlinux-deps)): $(vmlinux-dirs) ;
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# Handle descending into subdirectories listed in $(vmlinux-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
|
|
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += $(vmlinux-dirs)
|
2005-09-12 04:30:22 +08:00
|
|
|
$(vmlinux-dirs): prepare scripts
|
2017-11-08 00:31:46 +08:00
|
|
|
$(Q)$(MAKE) $(build)=$@ need-builtin=1
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2013-07-11 21:34:51 +08:00
|
|
|
define filechk_kernel.release
|
|
|
|
|
echo "$(KERNELVERSION)$$($(CONFIG_SHELL) $(srctree)/scripts/setlocalversion $(srctree))"
|
|
|
|
|
endef
|
|
|
|
|
|
2013-06-28 17:27:31 +08:00
|
|
|
# Store (new) KERNELRELEASE string in include/config/kernel.release
|
2006-06-09 13:12:43 +08:00
|
|
|
include/config/kernel.release: include/config/auto.conf FORCE
|
2013-07-11 21:34:51 +08:00
|
|
|
$(call filechk,kernel.release)
|
2006-01-10 04:20:34 +08:00
|
|
|
|
2018-03-16 15:37:11 +08:00
|
|
|
# Additional helpers built in scripts/
|
|
|
|
|
# Carefully list dependencies so we do not try to build scripts twice
|
|
|
|
|
# in parallel
|
|
|
|
|
PHONY += scripts
|
|
|
|
|
scripts: scripts_basic include/config/auto.conf include/config/tristate.conf \
|
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 15:37:12 +08:00
|
|
|
asm-generic gcc-plugins $(autoksyms_h)
|
2018-03-16 15:37:11 +08:00
|
|
|
$(Q)$(MAKE) $(build)=$(@)
|
2006-01-10 04:20:34 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# Things we need to do before we recursively start building the kernel
|
2005-09-12 04:30:22 +08: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-17 06:20:36 +08:00
|
|
|
|
2005-09-12 04:30:22 +08:00
|
|
|
# Listed in dependency order
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += prepare archprepare prepare0 prepare1 prepare2 prepare3
|
2005-09-12 04:30:22 +08:00
|
|
|
|
2005-09-10 01:28:28 +08:00
|
|
|
# prepare3 is used to check if we are building in a separate output directory,
|
2005-04-17 06:20:36 +08:00
|
|
|
# and if so do:
|
|
|
|
|
# 1) Check that make has not been executed in the kernel src $(srctree)
|
2006-06-09 13:12:43 +08:00
|
|
|
prepare3: include/config/kernel.release
|
2005-04-17 06:20:36 +08:00
|
|
|
ifneq ($(KBUILD_SRC),)
|
2008-11-06 16:31:35 +08:00
|
|
|
@$(kecho) ' Using $(srctree) as source for kernel'
|
2006-06-09 13:12:39 +08:00
|
|
|
$(Q)if [ -f $(srctree)/.config -o -d $(srctree)/include/config ]; then \
|
2012-07-08 05:04:40 +08:00
|
|
|
echo >&2 " $(srctree) is not clean, please run 'make mrproper'"; \
|
|
|
|
|
echo >&2 " in the '$(srctree)' directory.";\
|
2005-04-17 06:20:36 +08:00
|
|
|
/bin/false; \
|
|
|
|
|
fi;
|
|
|
|
|
endif
|
|
|
|
|
|
2016-07-27 06:21:17 +08:00
|
|
|
# prepare2 creates a makefile if using a separate output directory.
|
|
|
|
|
# From this point forward, .config has been reprocessed, so any rules
|
|
|
|
|
# that need to depend on updated CONFIG_* values can be checked here.
|
|
|
|
|
prepare2: prepare3 prepare-compiler-check outputmakefile asm-generic
|
2005-04-17 06:20:36 +08:00
|
|
|
|
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 15:37:12 +08:00
|
|
|
prepare1: prepare2 $(version_h) $(autoksyms_h) include/generated/utsrelease.h \
|
2009-10-18 06:00:43 +08:00
|
|
|
include/config/auto.conf
|
2007-10-20 04:20:02 +08:00
|
|
|
$(cmd_crmodverdir)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2012-05-09 02:22:24 +08:00
|
|
|
archprepare: archheaders archscripts prepare1 scripts_basic
|
2005-09-12 04:30:22 +08:00
|
|
|
|
2016-05-24 06:09:38 +08:00
|
|
|
prepare0: archprepare gcc-plugins
|
2005-09-11 03:05:36 +08:00
|
|
|
$(Q)$(MAKE) $(build)=.
|
2005-09-10 01:28:28 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# All the preparing..
|
2016-02-29 12:22:42 +08:00
|
|
|
prepare: prepare0 prepare-objtool
|
|
|
|
|
|
2017-10-04 11:56:06 +08:00
|
|
|
# Support for using generic headers in asm-generic
|
|
|
|
|
PHONY += asm-generic uapi-asm-generic
|
|
|
|
|
asm-generic: uapi-asm-generic
|
|
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.asm-generic \
|
|
|
|
|
src=asm obj=arch/$(SRCARCH)/include/generated/asm
|
|
|
|
|
uapi-asm-generic:
|
|
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.asm-generic \
|
|
|
|
|
src=uapi/asm obj=arch/$(SRCARCH)/include/generated/uapi/asm
|
|
|
|
|
|
2016-02-29 12:22:42 +08:00
|
|
|
PHONY += prepare-objtool
|
2016-03-04 01:39:30 +08:00
|
|
|
prepare-objtool: $(objtool_target)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2016-07-27 06:21:17 +08:00
|
|
|
# Check for CONFIG flags that require compiler support. Abort the build
|
|
|
|
|
# after .config has been processed, but before the kernel build starts.
|
|
|
|
|
#
|
|
|
|
|
# For security-sensitive CONFIG options, we don't want to fallback and/or
|
|
|
|
|
# silently change which compiler flags will be used, since that leads to
|
|
|
|
|
# producing kernels with different security feature characteristics
|
|
|
|
|
# depending on the compiler used. (For example, "But I selected
|
|
|
|
|
# CC_STACKPROTECTOR_STRONG! Why did it build with _REGULAR?!")
|
|
|
|
|
PHONY += prepare-compiler-check
|
|
|
|
|
prepare-compiler-check: FORCE
|
|
|
|
|
# Make sure compiler supports requested stack protector flag.
|
|
|
|
|
ifdef stackp-name
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
# Warn about CONFIG_CC_STACKPROTECTOR_AUTO having found no option.
|
|
|
|
|
ifeq ($(stackp-flag),)
|
|
|
|
|
@echo CONFIG_CC_STACKPROTECTOR_$(stackp-name): \
|
|
|
|
|
Compiler does not support any known stack-protector >&2
|
|
|
|
|
else
|
|
|
|
|
# Fail if specifically requested stack protector is missing.
|
2016-07-27 06:21:17 +08:00
|
|
|
ifeq ($(call cc-option, $(stackp-flag)),)
|
|
|
|
|
@echo Cannot use CONFIG_CC_STACKPROTECTOR_$(stackp-name): \
|
|
|
|
|
$(stackp-flag) not supported by compiler >&2 && exit 1
|
|
|
|
|
endif
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
endif
|
2016-07-27 06:21:17 +08:00
|
|
|
endif
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
# Make sure compiler does not have buggy stack-protector support. If a
|
|
|
|
|
# specific stack-protector was requested, fail the build, otherwise warn.
|
2018-02-07 07:37:38 +08:00
|
|
|
ifdef stackp-broken
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
ifeq ($(stackp-name),AUTO)
|
|
|
|
|
@echo CONFIG_CC_STACKPROTECTOR_$(stackp-name): \
|
|
|
|
|
$(stackp-flag) available but compiler is broken: disabling >&2
|
|
|
|
|
else
|
2016-07-27 06:21:17 +08:00
|
|
|
@echo Cannot use CONFIG_CC_STACKPROTECTOR_$(stackp-name): \
|
|
|
|
|
$(stackp-flag) available but compiler is broken >&2 && exit 1
|
Makefile: introduce CONFIG_CC_STACKPROTECTOR_AUTO
Nearly all modern compilers support a stack-protector option, and nearly
all modern distributions enable the kernel stack-protector, so enabling
this by default in kernel builds would make sense. However, Kconfig does
not have knowledge of available compiler features, so it isn't safe to
force on, as this would unconditionally break builds for the compilers or
architectures that don't have support. Instead, this introduces a new
option, CONFIG_CC_STACKPROTECTOR_AUTO, which attempts to discover the best
possible stack-protector available, and will allow builds to proceed even
if the compiler doesn't support any stack-protector.
This option is made the default so that kernels built with modern
compilers will be protected-by-default against stack buffer overflows,
avoiding things like the recent BlueBorne attack. Selection of a specific
stack-protector option remains available, including disabling it.
Additionally, tiny.config is adjusted to use CC_STACKPROTECTOR_NONE, since
that's the option with the least code size (and it used to be the default,
so we have to explicitly choose it there now).
Link: http://lkml.kernel.org/r/1510076320-69931-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Laura Abbott <labbott@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-02-07 07:37:45 +08:00
|
|
|
endif
|
2016-07-27 06:21:17 +08:00
|
|
|
endif
|
|
|
|
|
@:
|
|
|
|
|
|
2005-04-17 06:20:36 +08: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-04 05:30:54 +08: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; \
|
|
|
|
|
(echo \#define UTS_RELEASE \"$(KERNELRELEASE)\";)
|
|
|
|
|
endef
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
define filechk_version.h
|
2012-02-17 05:49:15 +08:00
|
|
|
(echo \#define LINUX_VERSION_CODE $(shell \
|
|
|
|
|
expr $(VERSION) \* 65536 + 0$(PATCHLEVEL) \* 256 + 0$(SUBLEVEL)); \
|
2006-07-04 05:30:54 +08:00
|
|
|
echo '#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))';)
|
2005-04-17 06:20:36 +08:00
|
|
|
endef
|
|
|
|
|
|
2012-10-03 01:01:56 +08:00
|
|
|
$(version_h): $(srctree)/Makefile FORCE
|
2005-04-17 06:20:36 +08:00
|
|
|
$(call filechk,version.h)
|
2014-11-27 23:13:17 +08:00
|
|
|
$(Q)rm -f $(old_version_h)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-10-18 06:52:28 +08:00
|
|
|
include/generated/utsrelease.h: include/config/kernel.release FORCE
|
2006-07-04 05:30:54 +08:00
|
|
|
$(call filechk,utsrelease.h)
|
|
|
|
|
|
2008-12-16 19:33:43 +08:00
|
|
|
PHONY += headerdep
|
|
|
|
|
headerdep:
|
2011-04-27 05:17:11 +08:00
|
|
|
$(Q)find $(srctree)/include/ -name '*.h' | xargs --max-args 1 \
|
|
|
|
|
$(srctree)/scripts/headerdep.pl -I$(srctree)/include
|
2008-12-16 19:33:43 +08:00
|
|
|
|
2006-06-18 18:58:39 +08:00
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
# Kernel headers
|
|
|
|
|
|
2008-06-05 22:43:46 +08:00
|
|
|
#Default location for installed headers
|
|
|
|
|
export INSTALL_HDR_PATH = $(objtree)/usr
|
2006-09-25 05:16:03 +08:00
|
|
|
|
2017-10-04 11:56:04 +08:00
|
|
|
# If we do an all arch process set dst to include/arch-$(SRCARCH)
|
|
|
|
|
hdr-dst = $(if $(KBUILD_HEADERS), dst=include/arch-$(SRCARCH), dst=include)
|
2008-06-05 22:43:46 +08:00
|
|
|
|
2011-11-18 05:17:35 +08:00
|
|
|
PHONY += archheaders
|
|
|
|
|
archheaders:
|
|
|
|
|
|
2012-05-09 02:22:24 +08:00
|
|
|
PHONY += archscripts
|
|
|
|
|
archscripts:
|
|
|
|
|
|
2008-06-05 22:43:46 +08:00
|
|
|
PHONY += __headers
|
2017-07-10 02:32:59 +08:00
|
|
|
__headers: $(version_h) scripts_basic uapi-asm-generic archheaders archscripts
|
2011-03-15 14:34:25 +08:00
|
|
|
$(Q)$(MAKE) $(build)=scripts build_unifdef
|
2008-06-05 22:43:46 +08:00
|
|
|
|
|
|
|
|
PHONY += headers_install_all
|
2008-06-21 06:24:17 +08:00
|
|
|
headers_install_all:
|
|
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/headers.sh install
|
2006-09-25 05:16:03 +08:00
|
|
|
|
2006-06-18 18:58:39 +08:00
|
|
|
PHONY += headers_install
|
2008-06-05 22:43:46 +08:00
|
|
|
headers_install: __headers
|
2017-10-04 11:56:04 +08:00
|
|
|
$(if $(wildcard $(srctree)/arch/$(SRCARCH)/include/uapi/asm/Kbuild),, \
|
2012-10-03 01:01:57 +08:00
|
|
|
$(error Headers not exportable for the $(SRCARCH) architecture))
|
2017-07-10 02:32:35 +08:00
|
|
|
$(Q)$(MAKE) $(hdr-inst)=include/uapi dst=include
|
2017-10-04 11:56:04 +08:00
|
|
|
$(Q)$(MAKE) $(hdr-inst)=arch/$(SRCARCH)/include/uapi $(hdr-dst)
|
2006-06-18 18:58:39 +08:00
|
|
|
|
2007-02-14 16:33:02 +08:00
|
|
|
PHONY += headers_check_all
|
|
|
|
|
headers_check_all: headers_install_all
|
2008-06-21 06:24:17 +08:00
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/headers.sh check
|
2007-02-14 16:33:02 +08:00
|
|
|
|
2006-06-18 19:02:10 +08:00
|
|
|
PHONY += headers_check
|
|
|
|
|
headers_check: headers_install
|
2017-07-10 02:32:35 +08:00
|
|
|
$(Q)$(MAKE) $(hdr-inst)=include/uapi dst=include HDRCHECK=1
|
2017-10-04 11:56:04 +08:00
|
|
|
$(Q)$(MAKE) $(hdr-inst)=arch/$(SRCARCH)/include/uapi $(hdr-dst) HDRCHECK=1
|
2006-06-18 19:02:10 +08:00
|
|
|
|
2014-08-08 03:07:46 +08:00
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
# Kernel selftest
|
|
|
|
|
|
|
|
|
|
PHONY += kselftest
|
|
|
|
|
kselftest:
|
2017-09-07 06:44:35 +08:00
|
|
|
$(Q)$(MAKE) -C $(srctree)/tools/testing/selftests run_tests
|
2014-08-08 03:07:46 +08:00
|
|
|
|
2017-08-19 05:54:41 +08:00
|
|
|
PHONY += kselftest-clean
|
2015-10-08 10:41:18 +08:00
|
|
|
kselftest-clean:
|
2017-09-07 06:44:35 +08:00
|
|
|
$(Q)$(MAKE) -C $(srctree)/tools/testing/selftests clean
|
2015-10-08 10:41:18 +08:00
|
|
|
|
2016-01-08 15:27:34 +08:00
|
|
|
PHONY += kselftest-merge
|
|
|
|
|
kselftest-merge:
|
|
|
|
|
$(if $(wildcard $(objtree)/.config),, $(error No .config exists, config your kernel first!))
|
|
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/kconfig/merge_config.sh \
|
|
|
|
|
-m $(objtree)/.config \
|
|
|
|
|
$(srctree)/tools/testing/selftests/*/config
|
|
|
|
|
+$(Q)$(MAKE) -f $(srctree)/Makefile olddefconfig
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
# Modules
|
|
|
|
|
|
|
|
|
|
ifdef CONFIG_MODULES
|
|
|
|
|
|
2006-06-25 06:07:55 +08:00
|
|
|
# By default, build modules as well
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2010-03-10 19:28:58 +08:00
|
|
|
all: modules
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2014-04-28 15:32:43 +08:00
|
|
|
# Build modules
|
2007-12-07 20:04:30 +08:00
|
|
|
#
|
2014-04-28 15:32:43 +08: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-17 06:20:36 +08:00
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += modules
|
2010-06-08 04:22:12 +08:00
|
|
|
modules: $(vmlinux-dirs) $(if $(KBUILD_BUILTIN),vmlinux) modules.builtin
|
2007-12-07 20:04:30 +08:00
|
|
|
$(Q)$(AWK) '!x[$$0]++' $(vmlinux-dirs:%=$(objtree)/%/modules.order) > $(objtree)/modules.order
|
2008-11-06 16:31:35 +08:00
|
|
|
@$(kecho) ' Building modules, stage 2.';
|
2006-08-09 03:36:08 +08:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2010-03-08 17:07:12 +08:00
|
|
|
modules.builtin: $(vmlinux-dirs:%=%/modules.builtin)
|
|
|
|
|
$(Q)$(AWK) '!x[$$0]++' $^ > $(objtree)/modules.builtin
|
|
|
|
|
|
2010-03-10 19:28:58 +08:00
|
|
|
%/modules.builtin: include/config/auto.conf
|
2010-03-08 17:07:12 +08:00
|
|
|
$(Q)$(MAKE) $(modbuiltin)=$*
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# Target to prepare building external modules
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += modules_prepare
|
2005-09-12 04:30:22 +08:00
|
|
|
modules_prepare: prepare scripts
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# Target to install modules
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += modules_install
|
2005-04-17 06:20:36 +08:00
|
|
|
modules_install: _modinst_ _modinst_post
|
|
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += _modinst_
|
2010-06-08 04:22:12 +08:00
|
|
|
_modinst_:
|
2005-04-17 06:20:36 +08:00
|
|
|
@rm -rf $(MODLIB)/kernel
|
|
|
|
|
@rm -f $(MODLIB)/source
|
|
|
|
|
@mkdir -p $(MODLIB)/kernel
|
2017-08-20 14:04:11 +08:00
|
|
|
@ln -s $(abspath $(srctree)) $(MODLIB)/source
|
2005-04-17 06:20:36 +08:00
|
|
|
@if [ ! $(objtree) -ef $(MODLIB)/build ]; then \
|
|
|
|
|
rm -f $(MODLIB)/build ; \
|
2014-04-25 23:29:45 +08:00
|
|
|
ln -s $(CURDIR) $(MODLIB)/build ; \
|
2005-04-17 06:20:36 +08:00
|
|
|
fi
|
2007-12-07 20:04:30 +08:00
|
|
|
@cp -f $(objtree)/modules.order $(MODLIB)/
|
2009-12-07 23:38:33 +08:00
|
|
|
@cp -f $(objtree)/modules.builtin $(MODLIB)/
|
2006-08-09 03:36:08 +08:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modinst
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-19 03:24:21 +08:00
|
|
|
# This depmod is only for convenience to give the initial
|
2005-04-17 06:20:36 +08:00
|
|
|
# boot a modules.dep even before / is mounted read-write. However the
|
|
|
|
|
# boot script depmod is the master version.
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += _modinst_post
|
2013-07-11 10:02:51 +08:00
|
|
|
_modinst_post: _modinst_
|
2007-10-19 03:24:21 +08:00
|
|
|
$(call cmd,depmod)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2012-11-05 06:39:24 +08:00
|
|
|
ifeq ($(CONFIG_MODULE_SIG), y)
|
|
|
|
|
PHONY += modules_sign
|
|
|
|
|
modules_sign:
|
|
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modsign
|
|
|
|
|
endif
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
else # CONFIG_MODULES
|
|
|
|
|
|
|
|
|
|
# Modules not configured
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
2016-03-13 08:39:22 +08:00
|
|
|
PHONY += modules modules_install
|
|
|
|
|
modules modules_install:
|
2012-07-08 05:04:40 +08: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-17 06:20:36 +08: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'
|
2018-03-16 15:37:14 +08:00
|
|
|
CLEAN_DIRS += $(MODVERDIR) include/ksym
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# Directories & files removed with 'make mrproper'
|
2011-04-28 04:29:49 +08:00
|
|
|
MRPROPER_DIRS += include/config usr/include include/generated \
|
2014-04-28 15:32:43 +08:00
|
|
|
arch/*/include/generated .tmp_objdiff
|
2017-09-22 13:31:13 +08:00
|
|
|
MRPROPER_FILES += .config .config.old .version \
|
2012-10-02 13:05:24 +08:00
|
|
|
Module.symvers tags TAGS cscope* GPATH GTAGS GRTAGS GSYMS \
|
2015-07-21 04:16:30 +08:00
|
|
|
signing_key.pem signing_key.priv signing_key.x509 \
|
|
|
|
|
x509.genkey extra_certificates signing_key.x509.keyid \
|
2015-02-18 05:46:36 +08:00
|
|
|
signing_key.x509.signer vmlinux-gdb.py
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# clean - Delete most, but leave enough to build external modules
|
|
|
|
|
#
|
|
|
|
|
clean: rm-dirs := $(CLEAN_DIRS)
|
|
|
|
|
clean: rm-files := $(CLEAN_FILES)
|
2012-02-04 17:55:59 +08:00
|
|
|
clean-dirs := $(addprefix _clean_, . $(vmlinux-alldirs) Documentation samples)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2012-10-29 19:23:02 +08:00
|
|
|
PHONY += $(clean-dirs) clean archclean vmlinuxclean
|
2005-04-17 06:20:36 +08:00
|
|
|
$(clean-dirs):
|
|
|
|
|
$(Q)$(MAKE) $(clean)=$(patsubst _clean_%,%,$@)
|
|
|
|
|
|
2012-10-29 19:23:02 +08:00
|
|
|
vmlinuxclean:
|
|
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/link-vmlinux.sh clean
|
2016-08-24 20:29:21 +08:00
|
|
|
$(Q)$(if $(ARCH_POSTLINK), $(MAKE) -f $(ARCH_POSTLINK) clean)
|
2012-10-29 19:23:02 +08:00
|
|
|
|
|
|
|
|
clean: archclean vmlinuxclean
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# mrproper - Delete all generated files, including .config
|
|
|
|
|
#
|
|
|
|
|
mrproper: rm-dirs := $(wildcard $(MRPROPER_DIRS))
|
|
|
|
|
mrproper: rm-files := $(wildcard $(MRPROPER_FILES))
|
2017-05-14 22:50:01 +08:00
|
|
|
mrproper-dirs := $(addprefix _mrproper_,scripts)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += $(mrproper-dirs) mrproper archmrproper
|
2005-04-17 06:20:36 +08:00
|
|
|
$(mrproper-dirs):
|
|
|
|
|
$(Q)$(MAKE) $(clean)=$(patsubst _mrproper_%,%,$@)
|
|
|
|
|
|
|
|
|
|
mrproper: clean archmrproper $(mrproper-dirs)
|
|
|
|
|
$(call cmd,rmdirs)
|
|
|
|
|
$(call cmd,rmfiles)
|
|
|
|
|
|
|
|
|
|
# distclean
|
|
|
|
|
#
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += distclean
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
distclean: mrproper
|
|
|
|
|
@find $(srctree) $(RCS_FIND_IGNORE) \
|
2006-06-25 06:07:55 +08:00
|
|
|
\( -name '*.orig' -o -name '*.rej' -o -name '*~' \
|
2017-01-22 22:02:32 +08:00
|
|
|
-o -name '*.bak' -o -name '#*#' -o -name '*%' \
|
|
|
|
|
-o -name 'core' \) \
|
2005-04-17 06:20:36 +08:00
|
|
|
-type f -print | xargs rm -f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Packaging of the kernel to various formats
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
# rpm target kept for backward compatibility
|
2014-07-05 04:53:52 +08:00
|
|
|
package-dir := scripts/package
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2010-06-07 18:44:25 +08:00
|
|
|
%src-pkg: FORCE
|
|
|
|
|
$(Q)$(MAKE) $(build)=$(package-dir) $@
|
2006-06-09 13:12:37 +08:00
|
|
|
%pkg: include/config/kernel.release FORCE
|
2006-03-21 14:22:35 +08:00
|
|
|
$(Q)$(MAKE) $(build)=$(package-dir) $@
|
2017-11-15 17:19:20 +08:00
|
|
|
rpm: rpm-pkg
|
|
|
|
|
@echo " WARNING: \"rpm\" target will be removed after Linux 4.18"
|
|
|
|
|
@echo " Please use \"rpm-pkg\" instead."
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
# Brief documentation of the typical targets used
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
2008-04-07 04:16:07 +08:00
|
|
|
boards := $(wildcard $(srctree)/arch/$(SRCARCH)/configs/*_defconfig)
|
2014-10-28 21:18:20 +08:00
|
|
|
boards := $(sort $(notdir $(boards)))
|
2008-04-07 04:16:07 +08:00
|
|
|
board-dirs := $(dir $(wildcard $(srctree)/arch/$(SRCARCH)/configs/*/*_defconfig))
|
|
|
|
|
board-dirs := $(sort $(notdir $(board-dirs:/=)))
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2016-03-13 08:39:55 +08:00
|
|
|
PHONY += help
|
2005-04-17 06:20:36 +08:00
|
|
|
help:
|
|
|
|
|
@echo 'Cleaning targets:'
|
2006-12-13 02:09:40 +08:00
|
|
|
@echo ' clean - Remove most generated files but keep the config and'
|
2006-09-24 20:01:08 +08:00
|
|
|
@echo ' enough build support to build external modules'
|
2006-12-13 02:09:40 +08:00
|
|
|
@echo ' mrproper - Remove all generated files + config + various backup files'
|
2006-09-24 20:01:08 +08:00
|
|
|
@echo ' distclean - mrproper + remove editor backup and patch files'
|
2005-04-17 06:20:36 +08: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-24 03:11:34 +08:00
|
|
|
@echo ' modules_install - Install all modules to INSTALL_MOD_PATH (default: /)'
|
2005-04-17 06:20:36 +08:00
|
|
|
@echo ' dir/ - Build all files in dir and below'
|
2015-12-11 00:35:19 +08:00
|
|
|
@echo ' dir/file.[ois] - Build specified target only'
|
2017-04-25 04:04:58 +08:00
|
|
|
@echo ' dir/file.ll - Build the LLVM assembly file'
|
|
|
|
|
@echo ' (requires compiler support for LLVM assembly generation)'
|
2010-01-14 01:31:44 +08: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 08:56:08 +08:00
|
|
|
@echo ' dir/file.ko - Build module including final link'
|
2009-04-25 00:35:23 +08:00
|
|
|
@echo ' modules_prepare - Set up for building external modules'
|
2005-04-17 06:20:36 +08:00
|
|
|
@echo ' tags/TAGS - Generate tags file for editors'
|
|
|
|
|
@echo ' cscope - Generate cscope index'
|
2011-01-14 20:07:05 +08:00
|
|
|
@echo ' gtags - Generate GNU GLOBAL index'
|
2014-07-11 21:57:24 +08: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-21 06:24:17 +08:00
|
|
|
@echo ' headers_install - Install sanitised kernel headers to INSTALL_HDR_PATH'; \
|
2007-01-29 20:47:01 +08:00
|
|
|
echo ' (default: $(INSTALL_HDR_PATH))'; \
|
2008-06-21 06:24:17 +08:00
|
|
|
echo ''
|
2017-05-09 06:55:08 +08:00
|
|
|
@echo 'Static analysers:'
|
2005-04-17 06:20:36 +08:00
|
|
|
@echo ' checkstack - Generate a list of stack hogs'
|
|
|
|
|
@echo ' namespacecheck - Name space analysis on compiled kernel'
|
2007-11-15 04:34:55 +08:00
|
|
|
@echo ' versioncheck - Sanity check on version.h usage'
|
2007-11-05 04:01:55 +08:00
|
|
|
@echo ' includecheck - Check for duplicate included header files'
|
2007-08-25 05:04:56 +08:00
|
|
|
@echo ' export_report - List the usages of all exported symbols'
|
2008-12-16 19:33:43 +08:00
|
|
|
@echo ' headers_check - Sanity check on exported headers'
|
2010-06-06 23:15:01 +08:00
|
|
|
@echo ' headerdep - Detect inclusion cycles in headers'
|
2017-11-14 17:47:20 +08:00
|
|
|
@echo ' coccicheck - Check with Coccinelle'
|
2010-06-06 23:15:01 +08:00
|
|
|
@echo ''
|
2017-05-09 06:55:08 +08:00
|
|
|
@echo 'Kernel selftest:'
|
2014-08-08 03:07:46 +08:00
|
|
|
@echo ' kselftest - Build and run kernel selftest (run as root)'
|
|
|
|
|
@echo ' Build, install, and boot kernel before'
|
|
|
|
|
@echo ' running kselftest on it'
|
2015-10-08 10:41:18 +08:00
|
|
|
@echo ' kselftest-clean - Remove all generated kselftest files'
|
2017-10-07 08:17:52 +08:00
|
|
|
@echo ' kselftest-merge - Merge all the config dependencies of kselftest to existing'
|
2016-01-08 15:27:34 +08:00
|
|
|
@echo ' .config.'
|
2014-08-08 03:07:46 +08:00
|
|
|
@echo ''
|
2017-05-09 06:55:08 +08:00
|
|
|
@echo 'Userspace tools targets:'
|
|
|
|
|
@echo ' use "make tools/help"'
|
|
|
|
|
@echo ' or "cd tools; make help"'
|
|
|
|
|
@echo ''
|
2005-04-17 06:20:36 +08:00
|
|
|
@echo 'Kernel packaging:'
|
2006-03-21 14:22:35 +08:00
|
|
|
@$(MAKE) $(build)=$(package-dir) help
|
2005-04-17 06:20:36 +08:00
|
|
|
@echo ''
|
|
|
|
|
@echo 'Documentation targets:'
|
2017-05-14 22:50:01 +08:00
|
|
|
@$(MAKE) -f $(srctree)/Documentation/Makefile dochelp
|
2005-04-17 06:20:36 +08:00
|
|
|
@echo ''
|
2008-04-26 10:34:58 +08:00
|
|
|
@echo 'Architecture specific targets ($(SRCARCH)):'
|
2005-04-17 06:20:36 +08:00
|
|
|
@$(if $(archhelp),$(archhelp),\
|
2008-04-26 10:34:58 +08:00
|
|
|
echo ' No architecture specific help defined for $(SRCARCH)')
|
2005-04-17 06:20:36 +08:00
|
|
|
@echo ''
|
|
|
|
|
@$(if $(boards), \
|
|
|
|
|
$(foreach b, $(boards), \
|
|
|
|
|
printf " %-24s - Build for %s\\n" $(b) $(subst _defconfig,,$(b));) \
|
|
|
|
|
echo '')
|
2008-04-07 04:16:07 +08: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-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
@echo ' make V=0|1 [targets] 0 => quiet build (default), 1 => verbose build'
|
2006-08-09 03:35:14 +08:00
|
|
|
@echo ' make V=2 [targets] 2 => give reason for rebuild of target'
|
2005-04-17 06:20:36 +08:00
|
|
|
@echo ' make O=dir [targets] Locate all output files in "dir", including .config'
|
2017-06-06 17:07:53 +08:00
|
|
|
@echo ' make C=1 [targets] Check re-compiled c source with $$CHECK (sparse by default)'
|
2006-05-24 04:57:23 +08:00
|
|
|
@echo ' make C=2 [targets] Force check of all c source with $$CHECK'
|
2011-06-16 19:26:23 +08:00
|
|
|
@echo ' make RECORDMCOUNT_WARN=1 [targets] Warn about ignored mcount sections'
|
2011-04-28 04:15:27 +08:00
|
|
|
@echo ' make W=n [targets] Enable extra gcc checks, n=1,2,3 where'
|
|
|
|
|
@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 20:45:31 +08:00
|
|
|
@echo ' Multiple levels can be combined with W=12 or W=123'
|
2005-04-17 06:20:36 +08:00
|
|
|
@echo ''
|
|
|
|
|
@echo 'Execute "make" or "make all" to build all targets marked with [*] '
|
|
|
|
|
@echo 'For further info see the ./README file'
|
|
|
|
|
|
|
|
|
|
|
2008-04-07 04:16:07 +08:00
|
|
|
help-board-dirs := $(addprefix help-,$(board-dirs))
|
|
|
|
|
|
|
|
|
|
help-boards: $(help-board-dirs)
|
|
|
|
|
|
2014-11-28 20:31:43 +08:00
|
|
|
boards-per-dir = $(sort $(notdir $(wildcard $(srctree)/arch/$(SRCARCH)/configs/$*/*_defconfig)))
|
2008-04-07 04:16:07 +08: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-17 06:20:36 +08:00
|
|
|
# Documentation targets
|
|
|
|
|
# ---------------------------------------------------------------------------
|
2017-10-09 23:26:15 +08: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 20:14:05 +08:00
|
|
|
PHONY += $(DOC_TARGETS)
|
|
|
|
|
$(DOC_TARGETS): scripts_basic FORCE
|
2017-05-14 22:50:01 +08:00
|
|
|
$(Q)$(MAKE) $(build)=Documentation $@
|
2005-04-17 06:20:36 +08: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-25 06:07:55 +08:00
|
|
|
# Install the modules built in the module directory
|
2005-04-17 06:20:36 +08:00
|
|
|
# Assumes install directory is already created
|
|
|
|
|
|
|
|
|
|
# We are always building modules
|
|
|
|
|
KBUILD_MODULES := 1
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += crmodverdir
|
2005-04-17 06:20:36 +08:00
|
|
|
crmodverdir:
|
2007-10-20 04:20:02 +08:00
|
|
|
$(cmd_crmodverdir)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += $(objtree)/Module.symvers
|
2005-04-17 06:20:36 +08:00
|
|
|
$(objtree)/Module.symvers:
|
|
|
|
|
@test -e $(objtree)/Module.symvers || ( \
|
|
|
|
|
echo; \
|
|
|
|
|
echo " WARNING: Symbol version dump $(objtree)/Module.symvers"; \
|
|
|
|
|
echo " is missing; modules will have no dependencies and modversions."; \
|
|
|
|
|
echo )
|
|
|
|
|
|
|
|
|
|
module-dirs := $(addprefix _module_,$(KBUILD_EXTMOD))
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += $(module-dirs) modules
|
2005-04-17 06:20:36 +08:00
|
|
|
$(module-dirs): crmodverdir $(objtree)/Module.symvers
|
|
|
|
|
$(Q)$(MAKE) $(build)=$(patsubst _module_%,%,$@)
|
|
|
|
|
|
|
|
|
|
modules: $(module-dirs)
|
2008-11-06 16:31:35 +08:00
|
|
|
@$(kecho) ' Building modules, stage 2.';
|
2006-08-09 03:36:08 +08:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += modules_install
|
2006-01-29 06:51:57 +08:00
|
|
|
modules_install: _emodinst_ _emodinst_post
|
2006-02-14 22:58:15 +08:00
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
install-dir := $(if $(INSTALL_MOD_DIR),$(INSTALL_MOD_DIR),extra)
|
|
|
|
|
PHONY += _emodinst_
|
2006-01-29 06:51:57 +08:00
|
|
|
_emodinst_:
|
|
|
|
|
$(Q)mkdir -p $(MODLIB)/$(install-dir)
|
2006-08-09 03:36:08 +08:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modinst
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += _emodinst_post
|
2006-01-29 06:51:57 +08:00
|
|
|
_emodinst_post: _emodinst_
|
|
|
|
|
$(call cmd,depmod)
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
clean-dirs := $(addprefix _clean_,$(KBUILD_EXTMOD))
|
|
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += $(clean-dirs) clean
|
2005-04-17 06:20:36 +08:00
|
|
|
$(clean-dirs):
|
|
|
|
|
$(Q)$(MAKE) $(clean)=$(patsubst _clean_%,%,$@)
|
|
|
|
|
|
|
|
|
|
clean: rm-dirs := $(MODVERDIR)
|
2010-09-06 18:00:08 +08:00
|
|
|
clean: rm-files := $(KBUILD_EXTMOD)/Module.symvers
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2016-03-13 08:39:55 +08:00
|
|
|
PHONY += help
|
2005-04-17 06:20:36 +08: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 14:13:18 +08:00
|
|
|
|
|
|
|
|
# Dummies...
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += prepare scripts
|
2006-01-25 14:13:18 +08:00
|
|
|
prepare: ;
|
|
|
|
|
scripts: ;
|
2005-04-17 06:20:36 +08:00
|
|
|
endif # KBUILD_EXTMOD
|
|
|
|
|
|
2010-09-06 18:00:08 +08:00
|
|
|
clean: $(clean-dirs)
|
|
|
|
|
$(call cmd,rmdirs)
|
|
|
|
|
$(call cmd,rmfiles)
|
2011-05-11 06:47:16 +08:00
|
|
|
@find $(if $(KBUILD_EXTMOD), $(KBUILD_EXTMOD), .) $(RCS_FIND_IGNORE) \
|
2017-11-17 00:49:13 +08:00
|
|
|
\( -name '*.[aios]' -o -name '*.ko' -o -name '.*.cmd' \
|
2017-11-02 10:51:25 +08:00
|
|
|
-o -name '*.ko.*' -o -name '*.dtb' -o -name '*.dtb.S' \
|
2017-11-17 00:49:13 +08:00
|
|
|
-o -name '*.dwo' -o -name '*.lst' \
|
2015-08-20 17:53:29 +08:00
|
|
|
-o -name '*.su' \
|
2010-09-06 18:00:08 +08:00
|
|
|
-o -name '.*.d' -o -name '.*.tmp' -o -name '*.mod.c' \
|
2018-03-23 21:04:31 +08:00
|
|
|
-o -name '*.lex.c' -o -name '*.tab.[ch]' \
|
2018-03-23 21:04:37 +08:00
|
|
|
-o -name '*.asn1.[ch]' \
|
2010-09-06 18:00:08 +08:00
|
|
|
-o -name '*.symtypes' -o -name 'modules.order' \
|
|
|
|
|
-o -name modules.builtin -o -name '.tmp_*.o.*' \
|
kbuild: Add a cache for generated variables
While timing a "no-op" build of the kernel (incrementally building the
kernel even though nothing changed) in the Chrome OS build system I
found that it was much slower than I expected.
Digging into things a bit, I found that quite a bit of the time was
spent invoking the C compiler even though we weren't actually building
anything. Currently in the Chrome OS build system the C compiler is
called through a number of wrappers (one of which is written in
python!) and can take upwards of 100 ms to invoke even if we're not
doing anything difficult, so these invocations of the compiler were
taking a lot of time. Worse the invocations couldn't seem to take
advantage of the multiple cores on my system.
Certainly it seems like we could make the compiler invocations in the
Chrome OS build system faster, but only to a point. Inherently
invoking a program as big as a C compiler is a fairly heavy
operation. Thus even if we can speed the compiler calls it made sense
to track down what was happening.
It turned out that all the compiler invocations were coming from
usages like this in the kernel's Makefile:
KBUILD_CFLAGS += $(call cc-option,-fno-delete-null-pointer-checks,)
Due to the way cc-option and similar statements work the above
contains an implicit call to the C compiler. ...and due to the fact
that we're storing the result in KBUILD_CFLAGS, a simply expanded
variable, the call will happen every time the Makefile is parsed, even
if there are no users of KBUILD_CFLAGS.
Rather than redoing this computation every time, it makes a lot of
sense to cache the result of all of the Makefile's compiler calls just
like we do when we compile a ".c" file to a ".o" file. Conceptually
this is quite a simple idea. ...and since the calls to invoke the
compiler and similar tools are centrally located in the Kbuild.include
file this doesn't even need to be super invasive.
Implementing the cache in a simple-to-use and efficient way is not
quite as simple as it first sounds, though. To get maximum speed we
really want the cache in a format that make can natively understand
and make doesn't really have an ability to load/parse files. ...but
make _can_ import other Makefiles, so the solution is to store the
cache in Makefile format. This requires coming up with a valid/unique
Makefile variable name for each value to be cached, but that's
solvable with some cleverness.
After this change, we'll automatically create a ".cache.mk" file that
will contain our cached variables. We'll load this on each invocation
of make and will avoid recomputing anything that's already in our
cache. The cache is stored in a format that it shouldn't need any
invalidation since anything that might change should affect the "key"
and any old cached value won't be used.
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Tested-by: Ingo Molnar <mingo@kernel.org>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2017-10-17 01:12:45 +08:00
|
|
|
-o -name .cache.mk \
|
2016-05-24 06:09:38 +08:00
|
|
|
-o -name '*.c.[012]*.*' \
|
2017-04-25 04:04:58 +08:00
|
|
|
-o -name '*.ll' \
|
2010-09-06 18:00:08 +08:00
|
|
|
-o -name '*.gcno' \) -type f -print | xargs rm -f
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
# Generate tags for editors
|
|
|
|
|
# ---------------------------------------------------------------------------
|
2008-12-04 05:24:13 +08:00
|
|
|
quiet_cmd_tags = GEN $@
|
|
|
|
|
cmd_tags = $(CONFIG_SHELL) $(srctree)/scripts/tags.sh $@
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2011-01-14 20:07:05 +08:00
|
|
|
tags TAGS cscope gtags: FORCE
|
2005-04-17 06:20:36 +08:00
|
|
|
$(call cmd,tags)
|
|
|
|
|
|
|
|
|
|
# Scripts to check various things for consistency
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
2011-04-27 05:15:01 +08:00
|
|
|
PHONY += includecheck versioncheck coccicheck namespacecheck export_report
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
includecheck:
|
2011-04-27 05:18:29 +08:00
|
|
|
find $(srctree)/* $(RCS_FIND_IGNORE) \
|
2005-04-17 06:20:36 +08:00
|
|
|
-name '*.[hcS]' -type f -print | sort \
|
2007-11-05 18:51:44 +08:00
|
|
|
| xargs $(PERL) -w $(srctree)/scripts/checkincludes.pl
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
versioncheck:
|
2011-04-27 05:19:28 +08:00
|
|
|
find $(srctree)/* $(RCS_FIND_IGNORE) \
|
2005-04-17 06:20:36 +08:00
|
|
|
-name '*.[hcS]' -type f -print | sort \
|
2007-11-05 18:51:44 +08:00
|
|
|
| xargs $(PERL) -w $(srctree)/scripts/checkversion.pl
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2010-06-06 23:15:01 +08:00
|
|
|
coccicheck:
|
|
|
|
|
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/$@
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
namespacecheck:
|
|
|
|
|
$(PERL) $(srctree)/scripts/namespace.pl
|
|
|
|
|
|
2007-08-25 05:04:56 +08:00
|
|
|
export_report:
|
|
|
|
|
$(PERL) $(srctree)/scripts/export_report.pl
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
endif #ifeq ($(config-targets),1)
|
|
|
|
|
endif #ifeq ($(mixed-targets),1)
|
|
|
|
|
|
2013-06-24 20:48:37 +08:00
|
|
|
PHONY += checkstack kernelrelease kernelversion image_name
|
2006-09-27 16:50:37 +08:00
|
|
|
|
2006-12-13 16:34:12 +08: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-17 06:20:36 +08:00
|
|
|
checkstack:
|
|
|
|
|
$(OBJDUMP) -d vmlinux $$(find . -name '*.ko') | \
|
2006-12-13 16:34:12 +08:00
|
|
|
$(PERL) $(src)/scripts/checkstack.pl $(CHECKSTACK_ARCH)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2010-08-20 17:36:06 +08:00
|
|
|
kernelrelease:
|
|
|
|
|
@echo "$(KERNELVERSION)$$($(CONFIG_SHELL) $(srctree)/scripts/setlocalversion $(srctree))"
|
2010-06-28 10:45:21 +08:00
|
|
|
|
2006-01-10 04:20:34 +08:00
|
|
|
kernelversion:
|
2006-01-16 19:12:12 +08:00
|
|
|
@echo $(KERNELVERSION)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2013-06-24 20:48:37 +08:00
|
|
|
image_name:
|
|
|
|
|
@echo $(KBUILD_IMAGE)
|
|
|
|
|
|
2012-04-12 00:36:18 +08:00
|
|
|
# Clear a bunch of variables before executing the submake
|
|
|
|
|
tools/: FORCE
|
2012-11-06 05:02:08 +08:00
|
|
|
$(Q)mkdir -p $(objtree)/tools
|
2017-08-20 14:04:11 +08:00
|
|
|
$(Q)$(MAKE) LDFLAGS= MAKEFLAGS="$(tools_silent) $(filter --j% -j,$(MAKEFLAGS))" O=$(abspath $(objtree)) subdir=tools -C $(src)/tools/
|
2012-04-12 00:36:18 +08:00
|
|
|
|
|
|
|
|
tools/%: FORCE
|
2012-11-06 05:02:08 +08:00
|
|
|
$(Q)mkdir -p $(objtree)/tools
|
2017-08-20 14:04:11 +08:00
|
|
|
$(Q)$(MAKE) LDFLAGS= MAKEFLAGS="$(tools_silent) $(filter --j% -j,$(MAKEFLAGS))" O=$(abspath $(objtree)) subdir=tools -C $(src)/tools/ $*
|
2012-04-12 00:36:18 +08:00
|
|
|
|
2006-01-25 14:13:18 +08:00
|
|
|
# Single targets
|
|
|
|
|
# ---------------------------------------------------------------------------
|
2006-04-05 18:57:21 +08:00
|
|
|
# Single targets are compatible with:
|
2008-02-03 21:14:02 +08:00
|
|
|
# - build with mixed source and output
|
2006-04-05 18:57:21 +08:00
|
|
|
# - build with separate output dir 'make O=...'
|
|
|
|
|
# - external modules
|
|
|
|
|
#
|
|
|
|
|
# target-dir => where to store outputfile
|
|
|
|
|
# build-dir => directory in kernel source tree to use
|
|
|
|
|
|
|
|
|
|
ifeq ($(KBUILD_EXTMOD),)
|
2006-04-06 14:25:31 +08:00
|
|
|
build-dir = $(patsubst %/,%,$(dir $@))
|
2006-04-05 18:57:21 +08:00
|
|
|
target-dir = $(dir $@)
|
|
|
|
|
else
|
|
|
|
|
zap-slash=$(filter-out .,$(patsubst %/,%,$(dir $@)))
|
|
|
|
|
build-dir = $(KBUILD_EXTMOD)$(if $(zap-slash),/$(zap-slash))
|
|
|
|
|
target-dir = $(if $(KBUILD_EXTMOD),$(dir $<),$(dir $@))
|
|
|
|
|
endif
|
|
|
|
|
|
2006-03-05 19:10:58 +08:00
|
|
|
%.s: %.c prepare scripts FORCE
|
2006-04-05 18:57:21 +08:00
|
|
|
$(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
|
2006-03-05 19:10:58 +08:00
|
|
|
%.i: %.c prepare scripts FORCE
|
2006-04-05 18:57:21 +08:00
|
|
|
$(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
|
2006-03-05 19:10:58 +08:00
|
|
|
%.o: %.c prepare scripts FORCE
|
2006-04-05 18:57:21 +08:00
|
|
|
$(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
|
2006-03-05 19:10:58 +08:00
|
|
|
%.lst: %.c prepare scripts FORCE
|
2006-04-05 18:57:21 +08:00
|
|
|
$(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
|
2006-03-05 19:10:58 +08:00
|
|
|
%.s: %.S prepare scripts FORCE
|
2006-04-05 18:57:21 +08:00
|
|
|
$(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
|
2006-03-05 19:10:58 +08:00
|
|
|
%.o: %.S prepare scripts FORCE
|
2006-04-05 18:57:21 +08:00
|
|
|
$(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
|
kbuild: support for %.symtypes files
Here is a patch that adds a new -T option to genksyms for generating dumps of
the type definition that makes up the symbol version hashes. This allows to
trace modversion changes back to what caused them. The dump format is the
name of the type defined, followed by its definition (which is almost C):
s#list_head struct list_head { s#list_head * next , * prev ; }
The s#, u#, e#, and t# prefixes stand for struct, union, enum, and typedef.
The exported symbols do not define types, and thus do not have an x# prefix:
nfs4_acl_get_whotype int nfs4_acl_get_whotype ( char * , t#u32 )
The symbol type defintion of a single file can be generated with:
make fs/jbd/journal.symtypes
If KBUILD_SYMTYPES is defined, all the *.symtypes of all object files that
export symbols are generated.
The single *.symtypes files can be combined into a single file after a kernel
build with a script like the following:
for f in $(find -name '*.symtypes' | sort); do
f=${f#./}
echo "/* ${f%.symtypes}.o */"
cat $f
echo
done \
| sed -e '\:UNKNOWN:d' \
-e 's:[,;] }:}:g' \
-e 's:\([[({]\) :\1:g' \
-e 's: \([])},;]\):\1:g' \
-e 's: $::' \
$f \
| awk '
/^.#/ { if (defined[$1] == $0) {
print $1
next
}
defined[$1] = $0
}
{ print }
'
When the kernel ABI changes, diffing individual *.symtype files, or the
combined files, against each other will show which symbol changes caused the
ABI changes. This can save a tremendous amount of time.
Dump the types that make up modversions
Signed-off-by: Andreas Gruenbacher <agruen@suse.de>
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
2006-05-10 02:37:30 +08:00
|
|
|
%.symtypes: %.c prepare scripts FORCE
|
|
|
|
|
$(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
|
2017-04-25 04:04:58 +08:00
|
|
|
%.ll: %.c prepare scripts FORCE
|
|
|
|
|
$(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
|
2006-01-25 14:13:18 +08:00
|
|
|
|
2006-04-05 18:57:21 +08:00
|
|
|
# Modules
|
2008-12-14 06:00:45 +08:00
|
|
|
/: prepare scripts FORCE
|
|
|
|
|
$(cmd_crmodverdir)
|
|
|
|
|
$(Q)$(MAKE) KBUILD_MODULES=$(if $(CONFIG_MODULES),1) \
|
|
|
|
|
$(build)=$(build-dir)
|
2014-09-26 02:23:58 +08:00
|
|
|
# Make sure the latest headers are built for Documentation
|
2016-07-04 22:39:35 +08:00
|
|
|
Documentation/ samples/: headers_install
|
2008-12-14 06:00:45 +08:00
|
|
|
%/: prepare scripts FORCE
|
2007-10-20 04:20:02 +08:00
|
|
|
$(cmd_crmodverdir)
|
2006-01-25 14:13:18 +08:00
|
|
|
$(Q)$(MAKE) KBUILD_MODULES=$(if $(CONFIG_MODULES),1) \
|
2006-04-05 18:57:21 +08:00
|
|
|
$(build)=$(build-dir)
|
|
|
|
|
%.ko: prepare scripts FORCE
|
2007-10-20 04:20:02 +08:00
|
|
|
$(cmd_crmodverdir)
|
2006-01-25 14:13:18 +08:00
|
|
|
$(Q)$(MAKE) KBUILD_MODULES=$(if $(CONFIG_MODULES),1) \
|
2006-04-05 18:57:21 +08:00
|
|
|
$(build)=$(build-dir) $(@:.ko=.o)
|
2006-08-09 03:36:08 +08:00
|
|
|
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
|
2006-01-25 14:13:18 +08:00
|
|
|
|
2014-04-28 15:26:18 +08:00
|
|
|
# FIXME Should go into a make.lib or something
|
2005-04-17 06:20:36 +08:00
|
|
|
# ===========================================================================
|
|
|
|
|
|
|
|
|
|
quiet_cmd_rmdirs = $(if $(wildcard $(rm-dirs)),CLEAN $(wildcard $(rm-dirs)))
|
|
|
|
|
cmd_rmdirs = rm -rf $(rm-dirs)
|
|
|
|
|
|
|
|
|
|
quiet_cmd_rmfiles = $(if $(wildcard $(rm-files)),CLEAN $(wildcard $(rm-files)))
|
|
|
|
|
cmd_rmfiles = rm -f $(rm-files)
|
|
|
|
|
|
2008-04-22 06:53:56 +08:00
|
|
|
# Run depmod only if we have System.map and depmod is executable
|
2007-10-19 03:24:21 +08:00
|
|
|
quiet_cmd_depmod = DEPMOD $(KERNELRELEASE)
|
2011-06-16 04:15:47 +08:00
|
|
|
cmd_depmod = $(CONFIG_SHELL) $(srctree)/scripts/depmod.sh $(DEPMOD) \
|
2013-03-15 12:34:17 +08:00
|
|
|
$(KERNELRELEASE) "$(patsubst y,_,$(CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX))"
|
2007-10-19 03:24:21 +08:00
|
|
|
|
2007-10-20 04:20:02 +08:00
|
|
|
# Create temporary dir for module support files
|
2007-10-22 17:23:07 +08:00
|
|
|
# clean it up only when building all modules
|
|
|
|
|
cmd_crmodverdir = $(Q)mkdir -p $(MODVERDIR) \
|
|
|
|
|
$(if $(KBUILD_MODULES),; rm -f $(MODVERDIR)/*)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
# read all saved command lines
|
|
|
|
|
|
2017-11-13 18:29:35 +08:00
|
|
|
cmd_files := $(wildcard .*.cmd $(foreach f,$(sort $(targets)),$(dir $(f)).$(notdir $(f)).cmd))
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
ifneq ($(cmd_files),)
|
|
|
|
|
$(cmd_files): ; # Do not try to update included dependency files
|
|
|
|
|
include $(cmd_files)
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
endif # skip-makefile
|
|
|
|
|
|
2006-03-06 06:14:10 +08:00
|
|
|
PHONY += FORCE
|
2005-04-17 06:20:36 +08:00
|
|
|
FORCE:
|
2006-03-06 06:14:10 +08:00
|
|
|
|
|
|
|
|
# Declare the contents of the .PHONY variable as phony. We keep that
|
2009-04-09 19:34:34 +08:00
|
|
|
# information in a variable so we can use it in if_changed and friends.
|
2006-03-06 06:14:10 +08:00
|
|
|
.PHONY: $(PHONY)
|