summaryrefslogtreecommitdiffstats
path: root/dynamic-layers
Commit message (Collapse)AuthorAgeFilesLines
* android-tools: make it work with devtoolEtienne Cordonnier2023-03-0743-137/+1143
| | | | | | | | | | devtool modify android-tools was failing with an error: - regenerate patches in the git format working with devtool - add debian patches to yocto instead of applying them manually with do_unpack_and_patch_debian, to make it work with devtool Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
* android-tools: fix libcrypto_utils link errorEtienne Cordonnier2023-03-061-1/+2
| | | | | | | | | | | | | | When building android-tools, this chain of dependency pulls the openssl library libcrypto.so.3 in recipe-sysroot: clang-native -> cmake-native -> curl-native -> openssl-native The issue is that libcrypto_utils attempt to link against the libcrypto.so produced by boringssl (debian/out/usr/lib/android/libcrypto.so), but the -L flags added by yocto to CPPFLAGS appear before the -L flag provided in the patch, and therefore the wrong library is used. Link explicitly against libcrypto.so.0 in order to ignore the openssl library and use boringssl instead. Note: to debug this add -Wl,--verbose to LDFLAGS Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
* android-tools: make native version compileEtienne Cordonnier2023-03-062-2/+4
| | | | | | | | | | | Those 2 warnings (caused by the combination of -nostdlib and the options added by meta-clang) were treated as errors: """ clang-14: warning: argument unused during compilation: '-rtlib=libgcc' [-Wunused-command-line-argument] clang-14: warning: argument unused during compilation: '--unwindlib=libgcc' [-Wunused-command-line-argument] """ Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
* android-tools-conf: fix typoEtienne Cordonnier2023-03-061-1/+1
| | | | Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
* android-tools-conf: remove PACKAGE_ARCH = MACHINE_ARCHEtienne Cordonnier2023-03-061-2/+0
| | | | | | | | | | | | android-tools inherits the native class, and RDEPENDS on android-tools-conf. This line causes an error when trying to build android-tools-native: """ ERROR: Required build target 'android-tools-native' has no buildable providers. Missing or unbuildable dependency chain was: ['android-tools-native', 'clang-native-x86_64'] """ Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
* android-tools: fix incremental builds by using ln -sfEtienne Cordonnier2023-03-0612-12/+12
| | | | | | | This avoids an error about the file already existing when debugging the recipe and starting incremental builds. Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
* android-tools: correctly pass DEB_HOST_ARCH to libbacktraceEtienne Cordonnier2023-03-062-5/+3
| | | | | | | | | | | - The code was producing the error "tool: command not found" and the else branch was always executed, even for libbacktrace. - There is no variable "deb_host_arch" defined in rules.yocto, so it's not clear what the first line of the patch with DEB_HOST_ARCH=${deb_host_arch} was supposed to do. "${deb_host_arch}" is always undefined in this context. Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
* android-tools: fix Upstream-Status formattingMartin Jansa2023-01-291-1/+1
| | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* bcc: Upgrade to 0.26.0Khem Raj2023-01-161-1/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Simplify ptest script and use posix syntaxMichal Wojcik2022-10-202-33/+29
| | | | Signed-off-by: Michal Wojcik <michal.wojcik@linaro.org>
* bpftrace: Disable ptests on riscv64Khem Raj2022-10-191-6/+13
| | | | | | | Clang crashes compiling some tests so until its fixed in riscv64 backend we have to disable it for atleast rv64 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Add ptest supportMichal Wojcik2022-10-173-1/+70
| | | | | | | | Use bcc cc and python test suites and parse their results in ptest form. Running whole suite on qemu may take up to 25 minutes, so running it with "ptest-runner -t 1800 bcc" is recommended. Signed-off-by: Michal Wojcik <michal.wojcik@linaro.org>
* bpftrace: Add ptest supportMichal Wojcik2022-09-302-3/+67
| | | | | | | | | Use existing bpftrace unit and runtime tests and parse their results in ptest form. Running whole suite may take up to 40 minutes, so running it with "ptest-runner -t 2400 bpftrace" is recommended. Signed-off-by: Michal Wojcik <michal.wojcik@linaro.org>
* bpftrace: Upgrade package to latest master (a277ec4)Michal Wojcik2022-09-291-1/+1
| | | | | | Include segfault workaround for LLVM 15 OpaquePointers (a277ec4). Signed-off-by: Michal Wojcik <michal.wojcik@linaro.org>
* bpftrace: Upgrade package to latest master (475ad59)Michal Wojcik2022-09-281-3/+2
| | | | | | Upgrade package to include segmentation fault fix added in bb2b5d8. Signed-off-by: Michal Wojcik <michal.wojcik@linaro.org>
* bpftrace: Upgrade to 0.16.0Khem Raj2022-09-072-214/+1
| | | | | | The patch is already applied upstream so drop it. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Upgrade to 0.25.0Khem Raj2022-08-141-1/+1
| | | | | | | Changes are here [1] [1] https://github.com/iovisor/bcc/releases/tag/v0.25.0 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* 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-272-0/+125
| | | | | | | | | | | | 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>
* bpftrace: Fix build with new libbpfKhem Raj2022-04-282-1/+214
| | | | | | | Fixes git/src/btf.cpp:651:10: error: no matching function for call to 'btf_dump__new' Signed-off-by: Khem Raj <raj.khem@gmail.com>
* android-tools: Use SPDX license naming conventionKhem Raj2022-03-081-1/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* 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>
* bpftrace: Upgrade to latest masterKhem Raj2022-02-211-4/+4
| | | | | | | Enable riscv64 as the support is now available this update is needed for it to work with clang14 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Upgrade to 0.24.0Khem Raj2022-02-165-68/+10
| | | | | | Drop upstreamed patch 0001-Remove-APInt-APSInt-toString-std-string-variants.patch Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Upgrade to 0.14.1Khem Raj2022-02-143-145/+10
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* android-tools: Fix syntax overridesAndrei Gherzan2021-12-091-10/+10
| | | | Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
* bcc: Add explicit dependency on flex target recipeSumit Garg2021-12-091-0/+1
| | | | | | | While building bcc for the target it depends on flex target recipe. So add that dependency explicity. Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
* bcc: Specify branch and protocol in git SRC_URIKhem Raj2021-11-051-1/+1
| | | | | | | | github has stopped supporting anonymous git protocol and bitbake now warns about branch not being explicit, master is no more a viable fallback Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Update to latest masterKhem Raj2021-09-163-45/+38
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Fix build with clang >= 13Khem Raj2021-09-053-7/+128
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Upgrade to latest on trunkKhem Raj2021-09-052-51/+1
| | | | | | Drop upstreamed patch Signed-off-by: Khem Raj <raj.khem@gmail.com>
* android-tools: convert to new override syntax.Bartłomiej Burdukiewicz2021-08-262-4/+4
| | | | Signed-off-by: Bartłomiej Burdukiewicz <bartlomiej.burdukiewicz@gmail.com>
* upgrade of android-tools to 10.0.0.r36Nisha Parrakat2021-08-1229-0/+1172
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An older version is present in the meta-oe layer. Took the old recipe and adapted it in the following way: --Deleted all the old patches that were applicable for old version. --Used all the makefiles that come with the new version directly from the source code, just modifying them to install output to a specific folder as below a)added rules_yocto.mk that will mimic the debian/rules b)modified the makefiles of the components to output to a common dir. c) Built boringssl crypto with the option -DOPENSSL_NO_ASM to solve the below errors libcrypto.so.0: undefined reference to `aes_hw_encrypt' libcrypto.so.0: undefined reference to `aes_hw_set_encrypt_key' libcrypto.so.0: undefined reference to `gcm_gmult_v8' libcrypto.so.0: undefined reference to `gcm_init_v8' libcrypto.so.0: undefined reference to `sha256_block_data_order' libcrypto.so.0: undefined reference to `aes_hw_ctr32_encrypt_blocks' libcrypto.so.0: undefined reference to `aes_hw_cbc_encrypt' libcrypto.so.0: undefined reference to `vpaes_decrypt' libcrypto.so.0: undefined reference to `vpaes_encrypt' libcrypto.so.0: undefined reference to `gcm_gmult_neon' libcrypto.so.0: undefined reference to `sha1_block_data_order' libcrypto.so.0: undefined reference to `sha512_block_data_order' libcrypto.so.0: undefined reference to `gcm_init_neon' libcrypto.so.0: undefined reference to `aes_hw_set_decrypt_key' libcrypto.so.0: undefined reference to `vpaes_set_decrypt_key' libcrypto.so.0: undefined reference to `gcm_ghash_neon' libcrypto.so.0: undefined reference to `bn_mul_mont' libcrypto.so.0: undefined reference to `aes_hw_decrypt' libcrypto.so.0: undefined reference to `gcm_ghash_v8' libcrypto.so.0: undefined reference to `vpaes_cbc_encrypt' libcrypto.so.0: undefined reference to `ChaCha20_ctr32' libcrypto.so.0: undefined reference to `vpaes_ctr32_encrypt_blocks' libcrypto.so.0: undefined reference to `vpaes_set_encrypt_key' Attention : https://github.com/grpc/grpc/issues/9440 d) compiled android compatible version of libunwind to be used to build libbacktrace e) REQUIRES meta-selinux for libselinux, thus added it to BBFILES_DYNAMIC of this layer. f) checked compilation and packaging for for x86_64 and aarch64 g) UNTESTED android-tools-adbd.service , couldn't find how to build adbd that is needed by the service with the new version of android-tools. At present the service is still packaged but may not work. h) tested the adb and fastboot on the core-image-minimal by including the android-tools in the image and ran the commands with 'help' Signed-off-by: Nisha Parrakat <Nisha.Parrakat@kpit.com> Signed-off-by: Nisha Parrakat <nishaparrakat@gmail.com>
* bpftrace: Update to masterKhem Raj2021-08-063-7/+57
| | | | | | Fix build with libc++ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Upgrade to 0.13.0Khem Raj2021-08-063-33/+33
| | | | | | | | Drop already upstreamed patch Fix build with clang 13 Add missing dependencies on systemtap and libcereal Signed-off-by: Khem Raj <raj.khem@gmail.com>
* meta-clang: Convert to new override syntaxSigned-off-by: Martin Jansa2021-08-034-14/+14
| | | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Fix build with llvm >= 13Khem Raj2021-06-142-0/+43
| | | | | | toString implementation has changed in LLVM Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Update to latestKhem Raj2021-06-141-1/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Update to master tipKhem Raj2021-06-089-913/+7
| | | | | | | | | | | | In order to use latest clang, latest bcc sources are needed, this also means that we need to use vendored libbpf as thats the newest one needed and avoids dependencies on kernel bpf headers which maybe old and out of sync examples use error.h header which is not available on musl therefore disable examples when building on musl Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Update to using master branchKhem Raj2021-03-312-2/+35
| | | | | | | | | This is needed for fixing builds with master since clang 12 has dropped ORCv1 APIs Add a patch to fix build with clang-12 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Drop browser-layer from dynamic layersKhem Raj2021-03-272-10/+0
| | | | | | | These changes have been proposed for meta-browser itself see https://github.com/OSSystems/meta-browser/pull/489 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: link with dynamic libbpfMatteo Croce2021-03-105-1/+542
| | | | | | | | | Link bcc dynamically against libbpf. This reduces the size of libbcc.so from 68 MB to 3 MB. Backport some patches from upstream which are needed for the actual dynamic linking. Signed-off-by: Matteo Croce <mcroce@microsoft.com>
* bcc: Disable luaJIT on ppc64Khem Raj2021-03-011-1/+5
| | | | | | | ppc64 port is not yet available, its proposed here https://github.com/LuaJIT/LuaJIT/pull/54 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Fix build with clang-12Khem Raj2021-02-143-0/+151
| | | | | | bring-in needed patches from upstream Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Update to 0.11.4 releaseKhem Raj2020-12-122-279/+2
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Upgrade 0.15.0 -> 0.17.0He Zhe2020-11-041-3/+1
| | | | | | To support kernel v5.9 and remove patches that have been merged upstream. Signed-off-by: He Zhe <zhe.he@windriver.com>
* bcc: override the PY_CMD_ESCAPEDMingli Yu2020-09-102-0/+47
| | | | | | | | | | | | | Override the PY_CMD_ESCAPED as the PY_CMD_ESCAPED is constructed by the full path of the python3. In some cases, the path is so long and result in the PY_CMD_ESCAPED exceeds 255 characters and comes below do_configure error: | CMake Error at src/python/CMakeLists.txt:18 (configure_file): | configure_file Problem configuring file | | CMake Error: Could not open file for write in copy operation /buildarea1/test/wr_build/wr1020_20200909_bcc/bcc_long_Kernel/auto-standalone_next/200827/lxbuilds/Intel-Snow-Ridge-NS_platform_up/intel-x86-64-standard-glibc-std/wrlinux/build/tmp-glibc/work/corei7-64-wrs-linux/bcc/0.15.0-r0/build/src/python/bcc--buildarea1-test-wr_build-wr1020_20200909_bcc-bcc_long_Kernel-auto-standalone_next-200827-lxbuilds-Intel-Snow-Ridge-NS_platform_up-intel-x86-64-standard-glibc-std-wrlinux-build-tmp-glibc-work-corei7-64-wrs-linux-bcc-0.15.0-r0-recipe-sysroot-native-usr-bin-python3-native-python3/bcc/version.py.tmp Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
* bcc: trace: Fix failing to exit loopsHe Zhe2020-08-142-0/+47
| | | | | | | | | | | | | | | | | | | | | | /usr/share/bcc/tools/trace do_sys_open -M 1 PID TID COMM FUNC 3740 3740 irqbalance do_sys_open Exception ignored on calling ctypes callback function: <function PerfEventArray.open_perf_buffer.<locals>.raw_cb at 0x7f7c9efea280> Traceback (most recent call last): File "/usr/lib64/python3.8/site-packages/bcc/table.py", line 685, in raw_cb_ callback(cpu, data, size) File "/usr/share/bcc/tools/trace", line 630, in print_event exit() File "/usr/lib64/python3.8/sitebuiltins.py", line 26, in __call_ raise SystemExit(code) SystemExit: None Class Probe::print_event is used as a callback of a ctypes wrapper. With Yocto latest python v3.8.5, the exception raised by exit() is ignored and thus trace cannot exit. Use os._exit(0) instead. Signed-off-by: He Zhe <zhe.he@windriver.com>
* bcc: biosnoop: Fix failing to attach to trace_req_completionHe Zhe2020-08-142-0/+170
| | | | | | | | | | | | | | | | | | /usr/share/bcc/tools/biosnoop cannot attach kprobe, probe entry may not exist Traceback (most recent call last): File "/usr/share/bcc/tools/biosnoop", line 162, in <module> b.attach_kprobe(event="blk_account_io_completion", File "/usr/lib64/python3.8/site-packages/bcc/_init_.py", line 660, in attach_kprobe raise Exception("Failed to attach BPF program %s to kprobe %s" % Exception: Failed to attach BPF program b'trace_req_completion' to kprobe b'blk_account_io_completion' The kernel function "blk_account_io_completion" is not available anymore as attach point of Kprobe as of kernel version 5.8.0. Therefore, after discussions, we decided to use function "blk_account_io_done" instead in every kprobe attachment to "blk_account_io_completion". Signed-off-by: He Zhe <zhe.he@windriver.com>
* bpftrace: upgrade 0.9.4 -> 0.11.0Ovidiu Panait2020-08-062-1/+279
| | | | | | | | | | | | Uprev bpftrace to v0.11.0: * Add patch to fix compilation with LLVM 11 * Add cmake option CMAKE_ENABLE_EXPORTS=1 to prevent stripping, in order to fix the following error: root@qemux86-64:~# bpftrace /usr/share/bpftrace/tools/biosnoop.bt Attaching 4 probes... Could not resolve symbol: /proc/self/exe:BEGIN_trigger Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-13 14:02:55 +0000