-
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
Cannot build Arpack on ArchLinux #75
Comments
I just found that
While on ArchLinux the files are
Why is it not using |
How did you install Julia? |
to retrieve the base image and run the container:
afterwards inside the container:
|
Please try to install the official release. This was discussed in #5 so I'll close here. |
I will do so, thanks. However I think this needs to be fixed (I guess upstream from the fellows who maintain the ArchLinux package) since ArchLinux is a popular distribution and the fact that I cannot use Julia out of the box is quite annoying. Installing things like e.g. |
I'd like to reference here for anyone else that is having this problem that a work-around fix for the time being is to copy libarpack from /usr/lib to the Arpack Julia library folder. This is what I have done, starting from Julia install:
This is what worked for me. I'm hoping that by going through this here someone else might be able to fix their Arch system for the time being. |
I'm on Arch and having this problem, but the exact same issue seems to happen on both OpenSUSE Tumbleweed and Ubuntu 19.10. Interestingly, if I manually build Julia from source, either from the v1.2.0 or v1.3.0 git tags, the issue doesn't happen. So something that apparently all major distros are doing in their build of Julia causes Arpack to not be instalable, but everything other package I've used works fine. |
I get the following error on ArchLinux, which I reproduced in a Docker environment, see below:
The
libarpack.so
are there:Here is the docker environment I used:
and then the usual comnand to install
Arpack.jl
:]add Arpack
The text was updated successfully, but these errors were encountered: