summaryrefslogtreecommitdiffstats
path: root/recipes-kernel/libbpf
Commit message (Collapse)AuthorAgeFilesLines
* bpftrace: Fix llvm-objcopy issue and backport libbpf patches for ↵Soumya Sambu2025-03-268-1/+837
| | | | | | | | | | | | | | | | | | | | | | kirkstone-clang18 Fix bpftrace do_configure failure for kirkstone-clang18: | CMake Error at tests/data/CMakeLists.txt:6 (find_program): | Could not find LLVM_OBJCOPY using the following names: llvm-objcopy, | llvm-objcopy-18, llvm18-objcopy This error occurs because bpftrace searches for llvm-objcopy-${LLVM_VERSION_MAJOR}, expecting llvm version 18.x, while llvm-native from oe-core provides v13.0.1. Since clang-native provides v18.1.6, switching to it resolves the issue. While fixing this, additional libbpf compatibility issues were identified during bpftrace compilation, requiring backporting of multiple patches to resolve: • Undefined BTF_KIND_ENUM64, replaced with BTF_KIND_ENUM. • Missing kprobe_multi in bpf_link_create_opts. • Undefined BPF_TRACE_KPROBE_MULTI. • Undefined reference to btf_is_enum64 in libbpf.so and other related libbpf errors Signed-off-by: Soumya Sambu <soumya.sambu@windriver.com>
* libbpf: Backport bpf_btf_get_info_by_fdSoumya Sambu2025-03-262-0/+98
bcc v0.29.1 depends on bpf_btf_get_info_by_fd, which was introduced in libbpf v1.2.0. Since meta-oe kirkstone provides libbpf v0.7.0, this function was missing, resulting in a linker error in the bcc build: undefined reference to `bpf_btf_get_info_by_fd` This patch backports the necessary commit from libbpf v1.2.0 to v0.7.0, allowing bcc v0.29.1 to build successfully. Upstream patch: https://github.com/libbpf/libbpf/commit/30f6bc3c0a296638e3b6930dbcff6f1547f13997 Signed-off-by: Soumya Sambu <soumya.sambu@windriver.com>