-
Notifications
You must be signed in to change notification settings - Fork 53
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
Makefile incorrectly searches numpy #321
Comments
|
I think that's a Numpy 2 path. Can you try with Numpy < 2? |
but
so I think I need to adjust an include path. |
Here is the compile line:
I don't understand who constructs this. |
Hmm - this definitely looks like a numpy issue - similar to this one. May be this suggestion could solve the issue?
Will you please confirm that that fix works? |
@VictorEijkhout What version of numpy are you using? |
Numpy 2.0.1 And that fix makes things worse:
I think I need to add an include path, but I can't find where you set those. |
My fix:
|
Corrfunc hasn't yet been updated to support NumPy 2, but I took a quick stab at it and it seems to work (it builds and passes tests). I put it here if you'd like to try it: https://github.com/manodeep/Corrfunc/tree/numpy-2 It breaks NumPy 1 build support, which I'm not sure we want to do on main yet, so I'm going to leave it in a separate branch for now. Note that in that branch NumPy 2 is just a build dependency, and it should run with a recent NumPy 1 as well. |
Ahh never mind then. Looks like Lehman has a potential fix for numpy2 @lgarrison I made a suggestion on the commit - will you be able to check whether my suggestion works for both numpy1 and numpy2? |
@VictorEijkhout I merged in the numpy2 capability and made a new release. Do you mind checking whether the code now compiles with numpy2 (either from source or from the PyPI repo with Corrfunc v2.5.3)? |
I get an error on numpy headers not found, so I edit line 518 in common.mk to
which outputs
so I go searching for that directory:
Are you sure that path should exist?
The text was updated successfully, but these errors were encountered: