-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
numpy 1.14.3 can't open libf77blas.so.3 on Raspberry Pi Zero W (arm6) #11110
Comments
Where are you getting numpy in both the 1.14.3 and 1.12.1 cases? |
Thanks for commenting! Good question, took me quite a while to figure it out... Looks like they are installed from: https://www.piwheels.org/simple/numpy/numpy-1.12.1-cp35-cp35m-linux_armv6l.whl Here are the logs from the pip3 install, in case I have interpreted the logs incorrectly: numpy-1.12.1.txt These were generated in a new, clean virtual environment. I installed 1.12.1 first using: pip3 install numpy==1.12.1 -v --log numpy-1.12.1.txt That imports correctly into python3. Then I ran: pip3 install numpy==1.14.3 -v --log numpy-1.14.3.txt which has error: libf77blas.so.3: cannot open shared object file: No such file or directory |
So it's some 3rd party wheels. To solve the issue with their wheels,
you probably need to contact the piwheels people, whoever they are.
|
Thanks for getting back to me and sorry for troubling you. I'll see if I can alert them to the problem. |
Chances are you are missing a dependency
Give that a shot and then run it again. |
Closing. This is a downstream packaging issue, perhaps specific to @s7711 |
To other people getting this issue on raspi zero w: a solution is to install numpy via apt: pip3 uninstall numpy #remove previously installed package
apt install python3-numpy |
Thx, you saved my day! |
it works for me too! |
I'm using a Raspberry Pi Zero W and I am running Raspian Stretch Lite, released 2018-04-18, with update and dist-upgrade (on 17 May 2018). In python3 I've tried:
Didn't find any other comments on this, sorry if it is a duplicate.
The text was updated successfully, but these errors were encountered: