-
Notifications
You must be signed in to change notification settings - Fork 277
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
MPFR locating #903
Comments
Do you have multiple versions of |
As a potential fix, you could try to configure with |
Ok, that worked. Now I get the same problem with GMP: the |
Say, what happened to #321 ? Is that not yet in the latest release? |
Good point. @DrTimothyAldenDavis: Was that intentional? |
You know I just noticed that I was using the ?legacy? build where You and Tim will have to fight it out..... |
I can't recall. It was likely a mistake ... the primary SPEX repo is elsewhere and owned by someone else (I'm a collaborator). We do all the SPEX development on the other repo ( https://github.com/clouren/SPEX ) and then I copy major releases into the SuiteSparse repo and integrate them there. It's possible I accidentally overwrote this part. |
Ah ok. That makes sense. It would probably make sense to try and merge the changes from this repository (before that "merge" commit) and potential changes from the upstream repository in the two CMake modules in SPEX. |
Yes, I'll take a look at that. I will merge the two CMakeLists.txt files and post an update to it in the SPEX-3.3.0 branch ( https://github.com/clouren/SPEX/tree/SPEX-3.3.0 ). That's where our current development is going on. Alternatively, I could perhaps merge these changes into the SPEX-3.2.2 branch, which is a minor update from the stable v3.2.1 release of SPEX. It will take some juggling so I'll take care of it, one way or the other. |
Thanks for taking that on. Please, let me know if I can be of assistance. The relevant changes are probably mostly in the files As far as I can see, there haven't been any relevant changes to these files in the upstream repository. |
Looking at other parts of b09df58: |
it looks like I can just copy the updated FindGMP.cmake and FindMPFR.cmake files from that PR, into the SPEX/cmake_modules folder. It has a PREPEND instead of APPEND, though. Not sure which would be needed. |
Following the principle of "the user is always right", a |
It looks like the changes from 4f0af11 and ee6b694 are still lost with the latest version of these files in the I don't know what motivated those changes though. As far as I can tell, they would lead to a failing detection if these libraries can only be found in their static version (i.e., with those changes only shared gmp and mpfr libraries are accepted). @DrTimothyAldenDavis: Do you recall which issue(s) triggered these modifications to the detection logic? |
I'm pretty sure it was unintentional. The Spex development is done in a separate repo, and from time to time I copy over the code from there. I just accidentally over-wrote the update to the cmake module folder in SuiteSparse. I'll look at those commits and bring back the latest version from them. |
I can't recall which system/compiler/OS it was that I had to do that for. |
I've opened #905 with some follow-up changes for these CMake Find modules. |
I've merged in #905. I hope to post a beta release of SuiteSparse v7.9.0 soon, with these updates to SPEX, LAGraph, GraphBLAS, etc. |
@VictorEijkhout: Does using the pkg-config files of GMP and MPFR work for you again with SuiteSparse 7.9.0? |
Previous ticket 320 is un-re-openable.
and
but suitesparse still reports
This is the latest 7.8.3 release
The text was updated successfully, but these errors were encountered: