Closed leleliu008 closed 3 years ago
Thanks. Strange, I do not see this mentioned in their release notes. Have not installed clang-13 yet...
lang13 is the host cc, not Android ndk cc.
# If ARCH is not set, we use the host system's architecture for getarch compile options.
ifndef ARCH
HOSTARCH := $(shell uname -m)
else
HOSTARCH = $(ARCH)
endif
I think this logic is not correct. it should be changed to folloing:
HOSTARCH := $(shell uname -m)
clang13 is the host cc, not Android ndk cc.
Yes, certainly. "getarch" is always compiled to run on the host, as it is also needed to provide the cpu parameters when a specific TARGET was given on the command line.
I think this logic is not correct. it should be changed to folloing:
this was introduced to support compiling for 32bit on arm64 , maybe it is overly complicated but I do not think it is actually wrong ?
my host arch is aarch64
Oh. I did not expect that. Then setting HOSTARCH from ARCH would indeed be a problem (and maybe it was a coincidence that it did not break the arm/arm64 crossbuild, as the arm64 host may have been able to support 32bit binaries...). I guess I may have left that HOSTARCH=ARCH branch just to keep some compatibility with the previous version that was just using ARCH for everything. (Did not expect to make it bug-compatible though) So that would appear to be the actual cause, as the arm clang is known (if not documented) to not support "-march=native"
https://github.com/xianyi/OpenBLAS/archive/v0.3.18.tar.gz
android-ndk 23.0.7599858
error log:
Makefile.system L188-L193