| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
This ensures bundled gn is built propertly using gnu rumtime for build
host
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
The recipe has been patched to remove the clang dependency and moved to meta-openembedded at
https://github.com/openembedded/meta-openembedded/tree/master/meta-oe/dynamic-layers/selinux/recipes-devtool/android-tools
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
|
|
|
|
|
|
| |
Use system provided bpf and bcc
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
|
|
|
|
| |
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
|
|
|
|
|
|
|
|
| |
The fastboot makefile is creating the directory $(OUT_DIR)/usr/bin, so removing
fastboot from TOOLS_TO_BUILD in a bbappend resulted in a build failure
because of the missing directory $(OUT_DIR)/usr/bin.
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
- 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>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Michal Wojcik <michal.wojcik@linaro.org>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Include segfault workaround for LLVM 15 OpaquePointers (a277ec4).
Signed-off-by: Michal Wojcik <michal.wojcik@linaro.org>
|
|
|
|
|
|
| |
Upgrade package to include segmentation fault fix added in bb2b5d8.
Signed-off-by: Michal Wojcik <michal.wojcik@linaro.org>
|
|
|
|
|
|
| |
The patch is already applied upstream so drop it.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
Changes are here [1]
[1] https://github.com/iovisor/bcc/releases/tag/v0.25.0
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
| |
Disable LuaJIT on rv64 since its not yes ported
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Drop upstreamed patch 0001-Remove-APInt-APSInt-toString-std-string-variants.patch
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
| |
Drop upstreamed patch
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Bartłomiej Burdukiewicz <bartlomiej.burdukiewicz@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Fix build with libc++
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
| |
toString implementation has changed in LLVM
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|