summaryrefslogtreecommitdiffstats
path: root/dynamic-layers/selinux/android-tools/android-tools/use_name_space_std_to_compile_libbacktrace.patch
diff options
context:
space:
mode:
authorEtienne Cordonnier <ecordonnier@snap.com>2023-03-02 14:23:41 +0100
committerKhem Raj <raj.khem@gmail.com>2023-03-06 10:21:29 -0800
commit398d4bc3805ca1c5cbb845aacccdb8999aabeab4 (patch)
tree20d08819f8a4bab186877edfd6bf1bf584cd3832 /dynamic-layers/selinux/android-tools/android-tools/use_name_space_std_to_compile_libbacktrace.patch
parent39b89bbffe9e21bb2db5b2733b1f56610b6cdb45 (diff)
downloadmeta-clang-398d4bc3805ca1c5cbb845aacccdb8999aabeab4.tar.gz
android-tools: fix libcrypto_utils link error
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>
Diffstat (limited to 'dynamic-layers/selinux/android-tools/android-tools/use_name_space_std_to_compile_libbacktrace.patch')
0 files changed, 0 insertions, 0 deletions