-
Notifications
You must be signed in to change notification settings - Fork 1.6k
OpenBLAS , Build ARMV8 with clang. '../libopenblas_haswellp-r0.2.20.so' failed #1632
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
Comments
This looks as if the |
@martin-frbg
and then use belown command to build
However , the error still output |
Strange. Did you do |
@martin-frbg I did "make clean" and builded it again , but still not work. Anyway , I pasted the BUILD LOG as follow.
|
Sorry. AS= assembler, maybe it is finding the x86 one from your Ubuntu (from what I managed to find out, the "(EM:62)" part of the error message means "x86_64 format") . So I suggest you try with |
thx! @martin-frbg
is it right ? the new error issues output
Another question:
or
|
I think you need to try with |
@martin-frbg OK, i follow the second launch command order:
but output the new error issue:
the command used as follown :
Could you help me to check is it correct ?! |
Hmm. Error message from as seems to be "unknown option", and as it cannot build getarch we do not get Makefile.conf and other required information for the build. |
It uses host fortran compiler too set |
@martin-frbg and @brada4 BTW, android-ndk-r16b is no suitable for building android lib due to missing of some c header file Thanks for your help and Wait for next issue ~ |
Good to know it works for you now. You may want to update to the latest release (0.3.0) which has not yet been mentioned on the openblas.net homepage, 0.2.20 is a year old . 0.3.1 should be out in a matter of weeks, it will have a major rewrite of the thread setup code. |
Dear ~
To build the .so for android as command below ( refer to Build ARMV8 with clang ):
The platform & cofig. as follow:
But , get the error output as follown:
The text was updated successfully, but these errors were encountered: