Le 19/10/18 à 10:54, 殷啟聰 | Kai-Chung Yan a écrit :
Any reasons why fastboot is linked againt the bundled libraries of
android?
Those libraries (e.g. liblog, libutils) are used by Android SDK only and not
for general use, and due to their generic SONAME it would be unwise to put them
in `/usr/lib`, so we put them in a dedicated directory.
Please link against the system libraries.
What do you mean? `fastboot` and all other Android SDK components use the
system libraries, for example `glibc` and `pthread`.
OK, so it's actually not a direct dependency, but installing fastboot
pulls android-libselinux, android-libsepol and android-libunwind (and
maybe other)
$ aptitude why android-libselinux
iB fastboot Dépend android-libext4-utils
idA android-libext4-utils Dépend android-libselinux
$ aptitude why android-libsepol
iB fastboot Dépend android-libext4-utils
idA android-libext4-utils Dépend android-libselinux
idA android-libselinux Dépend android-libsepol
$ aptitude why android-libunwind
iB fastboot Dépend android-libziparchive
i A android-libziparchive Dépend android-libutils
i A android-libutils Dépend android-libbacktrace
i A android-libbacktrace Dépend android-libunwind
All of these already exist in the archive: libselinux1, libsepol1,
libunwind8
