-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
errors when build openblas for android-24 with clang #1513
Comments
What command line do you pass to make/cmake? |
The whole command are as below, I did it as the instructions on the website: # Set path to ndk-bundle
export NDK_BUNDLE_DIR=/home/usr/software/android-ndk-r14b
# Export PATH to contain directories of clang and aarch64-linux-android-*
# utilities
export PATH=${NDK_BUNDLE_DIR}/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/bin/:${NDK_BUNDLE_DIR}/toolchains/llvm/prebuilt/linux-x86_64/bin:$PATH
# Setup LDFLAGS so that loader can find libgcc and pass -lm for sqrt
export LDFLAGS="-L${NDK_BUNDLE_DIR}/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/lib/gcc/aarch64-linux-android/4.9.x
-lm"
# Setup the clang cross compile options
export CLANG_FLAGS="-target aarch64-linux-android --sysroot ${NDK_BUNDLE_DIR}/platforms/android-24/arch-arm64 -gcc-toolchain ${NDK_BUNDLE_DIR}/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/"
# Compile
make TARGET=ARMV8 ONLY_CBLAS=1 AR=ar CC="aarch64-linux-android-gcc ${CLANG_FLAGS}" HOSTCC=gcc NOFORTRAN=1
|
Can you try adding FC=FAKE |
I do not think it would try to find a fortran compiler when NOFORTRAN=1 is set. |
@martin-frbg yes, I have perl installed.
|
@brada4 It worked now when add FC=FAKE. |
I silently stumbled on that issue long ago without digging the cause, |
I cannot reproduce this problem when using a standalone toolchain, my build log starts with "detecting fortran compiler failed" (despite gfortran being available in the host) when NOFORTRAN=1 is given. |
Still works for me even when I set FC=/usr/bin/gfortran, and I do not see any loophole (except the potential trap that most NO_SOMETHING options have an underscore while NOFORTRAN does not) |
@martin-frbg I will try it some time later to check if I can reproduce the error. |
I do as the instruction said, and it can generate the static library, but it failed for building so files in the directory of exports. The error messages are given as follow:
PS: I tried both the git-develop version and the 0.2.20 release version, they had the same build errors.
The text was updated successfully, but these errors were encountered: