there is the detail：
[INFO] build jpeg in /e/bolt-master/third_party/android-aarch64/jpeg...
configure: WARNING: unrecognized options: --enable-neon
configure: WARNING: Assuming that char is signed on target machine.
If it is unsigned, this will be a little bit inefficient.
configure: WARNING: using cross tools not prefixed with host triplet
config.status: error: in /e/bolt-master/third_party/android-aarch64/jpeg/jpeg-9e': config.status: error: Something went wrong bootstrapping makefile fragments for automatic dependency tracking. If GNU make was not used, consider re-running the configure script with MAKE="gmake" (or whatever is necessary). You can also try re-running configure with the '--disable-dependency-tracking' option to at least be able to build the package (albeit without support for automatic dependency tracking). See config.log' for more details
there is the detail：
[INFO] build jpeg in /e/bolt-master/third_party/android-aarch64/jpeg...
configure: WARNING: unrecognized options: --enable-neon
configure: WARNING: Assuming that char is signed on target machine.
If it is unsigned, this will be a little bit inefficient.
configure: WARNING: using cross tools not prefixed with host triplet
config.status: error: in
/e/bolt-master/third_party/android-aarch64/jpeg/jpeg-9e': config.status: error: Something went wrong bootstrapping makefile fragments for automatic dependency tracking. If GNU make was not used, consider re-running the configure script with MAKE="gmake" (or whatever is necessary). You can also try re-running configure with the '--disable-dependency-tracking' option to at least be able to build the package (albeit without support for automatic dependency tracking). Seeconfig.log' for more details