-
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
Build fails on Ubuntu 20.04 aarch64 with undefined reference to 'WhereAmI' #4623
Comments
do you really need to build a version from almost five years ago ? |
set affinity with omp is absolutely unnecessary. Omp does manage affinity by itself. You need newer openblas, release from here or at least build dsc/dpkg from later/st ubuntu code. |
Thank you both for your input! I understand your points, but I need to maintain consistency with the environment described in a particular research paper. Therefore, I do need to build a version from almost five years ago. However, I will also try the latest version as suggested. I appreciate your and will close this issue. |
You need slow netlib lapack for consistency, openblas like any other accelerated library will diverge few bits precision from reference. |
Hmm, this is interesting. I suspect this problem persists in the current codebase, but is only triggered by NO_AFFINITY=0 |
IMO something following this? |
@brada4 no, not directly related to that. Setting up for handling affinity requires fetching the numerical ID of the cores each thread is running on, which is what WhereAmI is supposed to deliver. Unfortunately I'm not quite clear on how to parse the MPIDR_EL1 output on aarch64, a quick kludge would be to put the following function in common_arm64.h
or just make it
if you are on Linux with a fairly recent glibc |
Or noop it... |
strange suggestion when compiling with NO_AFFINITY=0 on purpose. |
Environment
Issue description
Encountered a build error when compiling OpenBLAS on aarch64 architecture. The specific error message is
Steps to Reproduce
Error Message
The build fails with the following output:
Log Files and output
see the attachment
The text was updated successfully, but these errors were encountered: