-
Notifications
You must be signed in to change notification settings - Fork 29
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 error with 1.0.3 on AARCH64 #54
Comments
Please provide the error message, all output from versioninfo and tell us how you installed Julia. |
Moved this comment into the description, where it was supposed to be. |
Does that mean that you've downloaded it from https://julialang.org/downloads/? Could you please try |
Downloaded from https://julialang-s3.julialang.org/bin/linux/aarch64/1.0/julia-1.0.3-linux-aarch64.tar.gz. I've since compiled 1.1.0-rc1 from tarball with dependencies and applied exactly the same fix to it.
If that isn't what you were looking for, or if you need the output from 1.0.3, I can get it this afternoon. |
@staticfloat Any ideas? |
Hello, Not sure if this helps but I have the same problem on OpenSuSE Tumbleweed(x86_64 not aarch64). I installed Julia from the package manager. Here is the output when I try to add Arpack:
And here is the output of versioninfo():
|
I just tried again with the generic binaries 1.0.3 on julialang.org and it worked without a problem. So it looks like more of a problem of the opensuse package than of Arpack itself. |
It is probably a little more complicated. See #5 for some context. |
@ericst please open a new issue; your issue is independent, likely related to #5, but I'm not certain. When you open a new issue, please provide as much context as you can. Regarding this issue, it looks like there's a bug in our Arpack.jl binaries; we told |
Compiling libopenblas with USE_BLAS64=1 on AARCH64 throws SEGV in blas testing. At least the 32bit intel and armv7 architectures are shipping libopenblas.so, too. |
@staticfloat done, it is #55. I am just starting out with julia, as soon as I know more I will look more into it. |
I have the same error as in the original post with the official Julia aarch64 binary using chrooted Arch Arm Linux on an Android tablet:
EDIT: EDIT2: |
Had the same issue on Nvidia Jetson TX2 (Aarch64), installing libarpack2 and copying libarpack.so.2.0.0 has fixed the issue with Julia LTS. |
Just ran into this myself, on an Nvidia Jetson Nano. It's an awesome demo system for Julia (cheap and CUDA works out of the box), would be great if Arpack could support Aarch64 without the workaround. |
@oschulz Are you using the official binaries? |
Yes, I tried with the official Julia v1.2-rc2 and v1.3-alpha binaries. Then I just ran |
@staticfloat Shouldn't have just worked? |
Yes, I think so, although I don't have a Jetson Nano to test with locally, so it's hard to say what could be going wrong. |
Ok, maybe I should test this again then, to make sure it wasn't a fluke. I'm travelling this week, will give it another try next week. |
@oschulz Is this still an issue? |
Ah, sorry for never getting back to your to this! Just tested is on a Jetson Xavier NX, all seems fine! I think this can be closed. |
as a result of Pkg.add("Gadfly") running in a Linux container on an armv8 chromebook. julia installed from the binary build for 1.0.3 on aarch64, running in the Crostini container on a Samsung Chromebook Plus.
ArpackBuilder builds versions of libarpack as if USE_BLAS64=1 had been specified, but there are archs that specify USE_BLAS64=0 in julia/Make.inc. The above error is thrown when Arpack dynamically loads its libarpack.so and cannot resolve the symbols created by USE_BLAS64=1 conventions. USE_BLAS64=1 specifies use of 64 bit integers when compiling libopenblas, renaming global symbols and the library binary itself with a _64 suffix.
A workaround is to trigger the build error, install the libarpack2 package from system repos, and copy the libarpack.so.2.0.0 binary from /usr/lib into .julia/packages/Arpack/.../deps/usr/lib.
This could be fixed by building both versions, USE_BLAS64={0,1}, of libarpack in ArpackBuilder, and deciding which to keep depending on whether this error gets thrown during the Arpack build. That might also work for the other open Arpack issues involving this error, too.
The text was updated successfully, but these errors were encountered: