diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-02-20 05:23:56 +0100 |
---|---|---|
committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-02-27 13:41:27 +0100 |
commit | bd55f96fa9fc29702ec30d75a4290bdadb00209d (patch) | |
tree | 8848f6aab1d11366e62a767e3e36dd4cf021c240 /init/Kconfig | |
parent | kbuild: hardcode genksyms path and remove GENKSYMS variable (diff) | |
download | linux-bd55f96fa9fc29702ec30d75a4290bdadb00209d.tar.xz linux-bd55f96fa9fc29702ec30d75a4290bdadb00209d.zip |
kbuild: refactor cc-cross-prefix implementation
- $(word 1, <text>) is equivalent to $(firstword <text>)
- hardcode "gcc" instead of $(CC)
- minimize the shell script part
A little more notes in case $(filter-out -%, ...) is not clear.
arch/mips/Makefile passes prefixes depending on the configuration.
CROSS_COMPILE := $(call cc-cross-prefix, $(tool-archpref)-linux- \
$(tool-archpref)-linux-gnu- $(tool-archpref)-unknown-linux-gnu-)
In the Kconfig stage (e.g. when you run 'make defconfig'), neither
CONFIG_32BIT nor CONFIG_64BIT is defined. So, $(tool-archpref) is
empty. As a result, "-linux -linux-gnu- -unknown-linux-gnu" is passed
into cc-cross-prefix. The command 'which' assumes arguments starting
with a hyphen as command options, then emits the following messages:
Illegal option -l
Illegal option -l
Illegal option -u
I think it is strange to define CROSS_COMPILE depending on the CONFIG
options since you need to feed $(CC) to Kconfig, but it is how MIPS
Makefile currently works. Anyway, it would not hurt to filter-out
invalid strings beforehand.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'init/Kconfig')
0 files changed, 0 insertions, 0 deletions