8dba7fefb0
When libbase is built for an APEX, it uses dlsym to reflectively access
liblog symbols that are added in R. This is because the APEX where
libbasse is packaged into might be running in pre-R devices where the
symbols don't exist in liblog.so.
This however causes a problem for a static executable in an APEX. Since
it is in an APEX, the dlsym is used. But libdl.so which provides dlsym
is not available to static executable. Currently, the dynamic linker is
the only executable in an APEX that all of its dependencies are
statically linked. Fixing the issue by providing fake dlsym by
statically linking to libdl.a.
Exempt-From-Owner-Approval: cherry-pick rvc-dev
Bug: 149569129
Test: m
Merged-In: I2e9e45d9876c2d6c878e541715389e6d1ef56996
(cherry picked from commit
|
||
---|---|---|
.. | ||
Android.bp | ||
libdl.cpp | ||
libdl.map.txt | ||
libdl_android.cpp | ||
libdl_android.map.txt | ||
libdl_cfi.cpp | ||
libdl_static.cpp | ||
MODULE_LICENSE_APACHE2 | ||
NOTICE |