-
Notifications
You must be signed in to change notification settings - Fork 89
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
MultiNest cmake error at CMakeLists #204
Comments
sounds similar to #189 |
Thanks, I looked into this issue, and if I understood correctly it was caused by a merge request and solved with a |
Did you try cleaning your build/ folder completely (including hidden files)? |
I used r |
|
ok,
Removing also .gitignore still gives the same error, but I can't delete the other two, I get
|
yeah, that's fine. So you still get the same error when doing |
yes, when I try |
Then I don't know. What OS is this? |
Linux, with
But I'm actually running on a cluster, so there might be some conflict |
Perhaps updating cmake could help. |
FYI I had this same problem and "solved" it using this thread: CMakeLists only checks for cmake > 2.8, but VERSION_GREATER_EQUAL was not introduced until cmake 3.7. I cannot update cmake on my system due to permissions, but I got it to run by changing VERSION_GREATER_EQUAL --> VERSION_GREATER (in 2 places). |
Hi,
I was trying to install MultiNest following the instructions here https://johannesbuchner.github.io/PyMultiNest/install.html, but when running
$cmake ..
I got the following errorLooking into /MultiNest/src/CMakeLists.txt I think the problem is that it doesn't recognize the variable CMAKE_FORTRAN_COMPILER_VERSION, since a similar error is given at line 46. A quick solution was commenting out lines 38-41 and 46-49, but I was wondering if there's a better way to make it work.
I've installed MultiNest other times before and this is the first one I'm getting this error. Also, I'm using cmake 2.8.12.2, which should meet the minimum requirements.
Thanks a lot in advance.
The text was updated successfully, but these errors were encountered: