diff options
author | Andrii Nakryiko <[email protected]> | 2021-02-03 12:34:45 -0800 |
---|---|---|
committer | Daniel Borkmann <[email protected]> | 2021-02-04 01:22:00 +0100 |
commit | 5f10c1aac8b29d225d19a74656865d1ee3db6eaa (patch) | |
tree | 156057eea4fbda61d0341f53d233e5dca3123884 /tools/testing/selftests/bpf/prog_tests/autoload.c | |
parent | 65e6dcf73398ddb64bb782ff2acd918d3a37a53a (diff) |
libbpf: Stop using feature-detection Makefiles
Libbpf's Makefile relies on Linux tools infrastructure's feature detection
framework, but libbpf's needs are very modest: it detects the presence of
libelf and libz, both of which are mandatory. So it doesn't benefit much from
the framework, but pays significant costs in terms of maintainability and
debugging experience, when something goes wrong. The other feature detector,
testing for the presernce of minimal BPF API in system headers is long
obsolete as well, providing no value.
So stop using feature detection and just assume the presence of libelf and
libz during build time. Worst case, user will get a clear and actionable
linker error, e.g.:
/usr/bin/ld: cannot find -lelf
On the other hand, we completely bypass recurring issues various users
reported over time with false negatives of feature detection (libelf or libz
not being detected, while they are actually present in the system).
Signed-off-by: Andrii Nakryiko <[email protected]>
Signed-off-by: Daniel Borkmann <[email protected]>
Acked-by: John Fastabend <[email protected]>
Acked-by: Randy Dunlap <[email protected]>
Link: https://lore.kernel.org/bpf/[email protected]
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions