aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/bpf/prog_tests/recursion.c
diff options
context:
space:
mode:
authorBjörn Töpel <[email protected]>2023-02-14 16:12:53 +0000
committerAlexei Starovoitov <[email protected]>2023-02-15 16:50:20 +0000
commit5e53e5c7edc6d69b8cb48b3b370cfe531e4b4132 (patch)
tree319b10cd27ea2dd7fab5b728fc4eb173c61be8d5 /tools/testing/selftests/bpf/prog_tests/recursion.c
parentbpf, docs: Add myself to BPF docs MAINTAINERS entry (diff)
downloadkernel-5e53e5c7edc6d69b8cb48b3b370cfe531e4b4132.tar.gz
kernel-5e53e5c7edc6d69b8cb48b3b370cfe531e4b4132.zip
selftests/bpf: Cross-compile bpftool
When the BPF selftests are cross-compiled, only the a host version of bpftool is built. This version of bpftool is used on the host-side to generate various intermediates, e.g., skeletons. The test runners are also using bpftool, so the Makefile will symlink bpftool from the selftest/bpf root, where the test runners will look the tool: | $(Q)ln -sf $(if $2,..,.)/tools/build/bpftool/bootstrap/bpftool \ | $(OUTPUT)/$(if $2,$2/)bpftool There are two problems for cross-compilation builds: 1. There is no native (cross-compilation target) of bpftool 2. The bootstrap/bpftool is never cross-compiled (by design) Make sure that a native/cross-compiled version of bpftool is built, and if CROSS_COMPILE is set, symlink the native/non-bootstrap version. Acked-by: Quentin Monnet <[email protected]> Signed-off-by: Björn Töpel <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Alexei Starovoitov <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/recursion.c')
0 files changed, 0 insertions, 0 deletions