diff options
author | 2024-11-01 09:27:11 +0100 | |
---|---|---|
committer | 2024-11-11 08:17:38 -0800 | |
commit | ec8d3b5c2adc356d3b34c0fe44a5be74022be037 (patch) | |
tree | 5e419dd2f790532fef4ee24e30b9f74500aac002 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | Merge tag 'perf-core-for-bpf-next' from tip tree (diff) | |
download | wireguard-linux-ec8d3b5c2adc356d3b34c0fe44a5be74022be037.tar.xz wireguard-linux-ec8d3b5c2adc356d3b34c0fe44a5be74022be037.zip |
selftests/bpf: Allow building with extra flags
In order to specify extra compilation or linking flags to BPF selftests,
it is possible to set EXTRA_CFLAGS and EXTRA_LDFLAGS from the command
line. The problem is that they are not propagated to sub-make calls
(runqslower, bpftool, libbpf) and in the better case are not applied, in
the worse case cause the entire build fail.
Propagate EXTRA_CFLAGS and EXTRA_LDFLAGS to the sub-makes.
This, for instance, allows to build selftests as PIE with
$ make EXTRA_CFLAGS='-fPIE' EXTRA_LDFLAGS='-pie'
Without this change, the command would fail because libbpf.a would not
be built with -fPIE and other PIE binaries would not link against it.
The only problem is that we have to explicitly provide empty
EXTRA_CFLAGS='' and EXTRA_LDFLAGS='' to the builds of kernel modules as
we don't want to build modules with flags used for userspace (the above
example would fail as kernel doesn't support PIE).
Signed-off-by: Viktor Malik <vmalik@redhat.com>
Reviewed-by: Toke Høiland-Jørgensen <toke@redhat.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions