liBlog | 一个基于Django1.11TLS版本的博客系统。自己的练手周边项目，会随时尝试新技术。

It's a problem of reqwest's version. Replace your original version with

From https://source.android.com/setup/develop/64-bit-builds :

LOCAL_MODULE_TARGET_ARCH

Set this variable to a list of architectures, such as arm x86 arm64. If the architecture being built is in that list, the current module is included by the build system.

LOCAL_MODULE_UNSUPPORTED_TARGET_ARCH

This variable is the opposite of LOCAL_MODULE_TARGET_ARCH. If the architecture being built is not in that list, the current module is included by the build system.

Based on this line

python: command not found

It seems it can't find python on your system

As the error message indicates your build system is missing libsqlite3.

There are two ways to solve this problem:

• Add libsqlite3-sys = { version = "0.18", features = ["bundled"]} to your Cargo.toml. This instructs the cargo to also build libsqlite3 as part of your application build. The library is statically linked using this method.

• Install libsqlite3 on the build system and use the SQLITE3_LIB_DIR environment variable to point the compiler to the correct directory. libsqlite3 will be linked dynamically, which means you also need to provide this library on the system you are running your application afterwards.

Answering own question for learning purposes: For the specifics of building for android, I was setting up the environment in another makefile. Because I have been making it by learning from various sources, some of it have been copy-paste and not put much thought into it as if they weren't explained they were things that were supposed to work.

What I tried was isolating all options that I did not know exactly why they were there for, which in my case were setting up specific flags, these ones in specific:

This can be a device specific issue. Vivo devices has number of issues with multiple applications. Try this with another device It will work fine.

Well, that was really hard, but we determine problem. That was problem in glibc compatibility. Build machine was jessie with libc-23 and working machine was jessie with libc-19 (at least I think, that was a problem, may be other system libs). We debug that very hard, we try to compile all our libraries with same options (build machine for forked libraries build them with -O2 and our libraries with -O0), not helped.

But when we move from jessie to debian stretch on both build and running - all starts to work fine (both have libc-24). That was hard and long, cause we have many libraries, but, that solved the problem. Hope, you will never stack in such problem.

... _liborwell/_libopenvpn3/openvpn3/libssl.a _liborwell/_libopenvpn3/openvpn3/libcrypto.a -lpthread _liborwell/_libopenvpn3/openvpn3/liblzo.a, - based on this sequence of libraries in the compiler command my best guess would be that you have a dependency on OpenSSL somewhere (in ${ORWELL_ANDROID_PROJECT_ROOT}/liborwell/ORWELL_INCLUDES.cmake?), which is probably configured to use pthreads. According to the description of its configuration system, it can be configured not to use threading at all:

[2] OpenSSL is built with threading capabilities unless the user specifies no-threads. The value of the key thread_scheme may be (unknown), in which case the user MUST give some compilation flags to Configure.

I also created android.mk in the dex2oat folder

This does not work. The pattern for declaring a module in an Android.mk would be, e.g. for creating a binary: