-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Installation issue: Cython compiler 'cython' cannot compile programs
when building py-scipy
#42940
Comments
Adding the conflict seems correct to me.
The concretization above and the attached Pythran 0.12.0 won't be tested well (if at all) with SciPy 1.11.4, since the metadata in https://github.com/scipy/scipy/blob/maintenance/1.11.x/pyproject.toml shows: # Reason for `<`: future-proofing (0.14.0 released and known to work)
"pythran>=0.12.0,<0.15.0",
|
Yeah, this is part of a larger environment (the goal is to try and build
Sorry, I'm not sure what you're suggesting exactly. Are you suggesting to change
py-pythran@0.12.2: ? I'm not sure that'd work because of the problem above with other py-alphafold deps.
|
You can also try #42213 which adds newer versions of many of these packages. |
Yes, that is what I was suggesting indeed. |
See https://spack.readthedocs.io/en/latest/build_settings.html#duplicate-nodes We would need to add |
Ok, the incompatibility of I'll open a PR to add the incompatibility of |
Update: I moved to another machine (I'm not going to touch the production one at this point 🥲) and got |
Steps to reproduce the issue
I think I'm running into two different issues with compiling
py-scipy
. First of all, due to serge-sans-paille/pythran#2101 I'm running into the errorreported at scipy/scipy#18390. I believe this one should be worked around by adding
to the
py-pythran
recipe in Spack. However, after that I still get another compilation errorError message
Error message
Information on your system
Additional information
spack-build-env.txt
spack-build-out.txt
CC: @adamjstewart @rgommers
General information
spack debug report
and reported the version of Spack/Python/Platformspack maintainers <name-of-the-package>
and @mentioned any maintainersThe text was updated successfully, but these errors were encountered: