diff options
author | Stefan Agner <stefan@agner.ch> | 2018-09-17 19:31:57 -0700 |
---|---|---|
committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-09-19 23:55:45 +0900 |
commit | ef8c4ed9db80261f397f0c0bf723684601ae3b52 (patch) | |
tree | 55514168f8e2ab1e547e0cfb90d6729a4c33151c /samples/Kconfig | |
parent | 5a4630aadb9a9525474e9ac92965829f990cb5c4 (diff) | |
download | linux-ef8c4ed9db80261f397f0c0bf723684601ae3b52.tar.gz linux-ef8c4ed9db80261f397f0c0bf723684601ae3b52.tar.bz2 linux-ef8c4ed9db80261f397f0c0bf723684601ae3b52.zip |
kbuild: allow to use GCC toolchain not in Clang search path
When using a GCC cross toolchain which is not in a compiled in
Clang search path, Clang reverts to the system assembler and
linker. This leads to assembler or linker errors, depending on
which tool is first used for a given architecture.
It seems that Clang is not searching $PATH for a matching
assembler or linker.
Make sure that Clang picks up the correct assembler or linker by
passing the cross compilers bin directory as search path.
This allows to use Clang provided by distributions with GCC
toolchains not in /usr/bin.
Link: https://github.com/ClangBuiltLinux/linux/issues/78
Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-and-tested-by: Nick Desaulniers <ndesaulniers@google.com>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'samples/Kconfig')
0 files changed, 0 insertions, 0 deletions