diff options
author | Andrii Nakryiko <andrii@kernel.org> | 2021-12-16 12:15:05 -0800 |
---|---|---|
committer | Andrii Nakryiko <andrii@kernel.org> | 2021-12-16 12:15:05 -0800 |
commit | 1a6369ba624929c8bfa412045af79dbf7703b8c8 (patch) | |
tree | 66fa0a1259577b2b61e1995785b186c3193423ed /include/linux/perf_event.h | |
parent | libbpf: Avoid reading past ELF data section end when copying license (diff) | |
parent | selftests/bpf: Enable cross-building with clang (diff) | |
download | linux-dev-1a6369ba624929c8bfa412045af79dbf7703b8c8.tar.xz linux-dev-1a6369ba624929c8bfa412045af79dbf7703b8c8.zip |
Merge branch 'tools/bpf: Enable cross-building with clang'
Jean-Philippe Brucker says:
====================
Since v1 [1], I added Quentin's acks and applied Andrii's suggestions:
* Pass CFLAGS to libbpf link in patch 3
* Substitute CLANG_CROSS_FLAGS whole in HOST_CFLAGS to avoid accidents,
patch 4
Add support for cross-building BPF tools and selftests with clang, by
passing LLVM=1 or CC=clang to make, as well as CROSS_COMPILE. A single
clang toolchain can generate binaries for multiple architectures, so
instead of having prefixes such as aarch64-linux-gnu-gcc, clang uses the
-target parameter: `clang -target aarch64-linux-gnu'.
Patch 1 adds the parameter in Makefile.include so tools can easily
support this. Patch 2 prepares for the libbpf change from patch 3 (keep
building resolve_btfids's libbpf in the host arch, when cross-building
the kernel with clang). Patches 3-6 enable cross-building BPF tools with
clang.
[1] https://lore.kernel.org/bpf/20211122192019.1277299-1-jean-philippe@linaro.org/
====================
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Diffstat (limited to 'include/linux/perf_event.h')
0 files changed, 0 insertions, 0 deletions