On 3/26/21 09:04, Nathan Chancellor wrote:
> From: John Millikin
>
> When cross-compiling with Clang, the `$(CLANG_FLAGS)' variable
> contains additional flags needed to build C and assembly sources
> for the target platform. Normally this variable is automatically
> included i
The following commit has been merged into the x86/build branch of tip:
Commit-ID: 8abe7fc26ad8f28bfdf78adbed56acd1fa93f82d
Gitweb:
https://git.kernel.org/tip/8abe7fc26ad8f28bfdf78adbed56acd1fa93f82d
Author:John Millikin
AuthorDate:Thu, 25 Mar 2021 17:04:33 -07:00
extensions.
Signed-off-by: John Millikin
---
Changes in v2:
- Reworded the commit message to highlight that this is for
cross-compilation.
- Removed the `ifdef CONFIG_CC_IS_CLANG' guard.
arch/x86/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
On 12/26/20 16:35, h...@zytor.com wrote:
> Why is CLANG_FLAGS non-null when unused? It would be better to centralize
> that.
CLANG_FLAGS normally propagates through inclusion in the default KBUILD_CFLAGS
and KBUILD_AFLAGS, set in `/Makefile':
# Makefile
KBUILD_CFLAGS += $(CLANG_FLAGS)
, because the LLVM assembler can't yet
parse certain GNU extensions.
* `--target' sets the target architecture when cross-compiling. This
flag must be set for both compilation and assembly (`KBUILD_AFLAGS')
to support architecture-specific assembler directives.
Signed-off-by: John Millikin
'
tool run successfully when using a non-GNU platform as a build host for
cross-compiling the kernel.
Signed-off-by: John Millikin
---
Helper binary to verify behavior for the current platform:
#include
#include
int main(int argc, char **argv) {
regex_t compiled
6 matches
Mail list logo
