summaryrefslogtreecommitdiffstats
path: root/dynamic-layers/openembedded-layer/recipes-devtools/bcc/bcc_0.24.0.bb
Commit message (Collapse)AuthorAgeFilesLines
* bcc: De-vendor libbpfDaniel Thompson2022-05-271-0/+2
| | | | | | | | | | | | | | | | | | | | | | | Currently bcc builds against a vendored copy of libbpf. This causes problems for bpftrace which is built against bcc and the system libbpf. The resulting version skew between the vendored and system versions of libbpf resulting in a SEGV whenever bpftrace is used. Although --help and -l (list probe points) work OK that is because they do not actually use BPF! Anything that does use BPF will crash immediately, including bpftrace --info and simple one-liners such as: ~# bpftrace -e 't:raw_syscalls:sys_exit { printf("%s", comm); }' Attaching 1 probe... Segmentation fault Note that this issue is very closely related to similar problems compiling bpftrace against mixed headers from the two libbpf versions. Fixes: https://github.com/iovisor/bpftrace/issues/2173 Fixes: bb3e56b06f9d ("bpftrace: Fix build with new libbpf") Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
* bcc: Fixes to allow libbpf to be de-vendoredDaniel Thompson2022-05-271-0/+1
| | | | | | | | | | | | De-vendoring libbpf resolves a SEGV everytime we run bpftrace. Unfortunately it is not currently possible to de-vendor libbpf because bcc does not build. Fix this with brute force and ignorance... and in a seperate patch so this can be treated as an explanation of the problem and ripped out in favour of the right fix. Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
* bcc: Enable riscv64 buildsKhem Raj2022-03-061-1/+2
| | | | | | Disable LuaJIT on rv64 since its not yes ported Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Upgrade to 0.24.0Khem Raj2022-02-161-0/+56
Drop upstreamed patch 0001-Remove-APInt-APSInt-toString-std-string-variants.patch Signed-off-by: Khem Raj <raj.khem@gmail.com>