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
Still unable to install scipy, after switch to local toolchain #359
Comments
Could you please try to install |
It's not a recommended practice to install dependencies directly into the installation directory. It's better to start with creating a virtualenv with
If you really wanted to install things into the installation directory as opposed to installing into a virtualenv, run
We periodically run tests of many popular python packages and we track the pass rate of their upstream tests. |
@msimacek I took all this advice, and I'm in a little bit better shape. It didn't work, but by also installing numpy 1.23.5 specifically suggested by @qunaibit I got past the failure I was seeing. Now it complains that it can't install ninja, another dependency. Is there maybe a known compatible version of ninja to specify as well? |
|
@msimacek okay actually the ninja failure was just a problem with cmake I guess, and I updating my system resolved it. scipy installation is still running, and has been for a while, we'll see what happens there... |
oh, now it finished. with the following error
|
Hmm, I've never seen that error. Could you please try with graalpy 23.1.0? |
Switching from 23.0.1 to 23.1.0 and repeating the steps results in some compilation failures. A subset of that is below, I can capture and post the entire output in another github gist if it would be useful.
|
scipy's code is incompatible with newer gfortran releases. You will have to |
I'll check if we could set that flag automatically in our patch (backport the check from current scipy). |
@timfel this variable did in fact fix it now its installed, and I'll do some experimentation with it and see how it goes. @msimacek it would be great if there was (1) a document somewhere with this tribal knowledge useful for things to build/install and (2) a docker image with things like scipy, torch, etc that are targeted for support so that there's a quick way to replicate that environment without having to know any workarounds. If either of these exist, maybe the readme can be updated to point at them. Otherwise though, I'm very excited to try this out. Thanks for your help. |
I finally got around to update the scipy patch so that meson should set the flag automatically when it's available, so this problem shouldn't happen anymore. |
Originally posted by @msimacek in #265 (comment)
After updating, I am still unable to install scipy. The ginstall command now says it isn't available, and pip also appears to be unavailable. If I use ginstall to install pip, I get a warning when using it:
But pip does not seem to ship with GraalPy.
Anyway, using the pip installed via ginstall to then install scipy still fails but does not seem to emit an entirely clear error message. You can see the full output in this gist:
https://gist.github.com/ashesfall/612c8ec7bef877f01e5b8e49df51ba76
Installing the failed requirement, numpy, by itself produces roughly similar behavior.
It seems odd to me that support for torch and scipy is mentioned as a long term goal in the readme, but there is no description of what an early experimenter should expect if they try and install either of these. I'd like to help out with the project in some way (at least through experimentation), but I don't know where to find a basic summary of the current expected behavior.
The text was updated successfully, but these errors were encountered: