-
Notifications
You must be signed in to change notification settings - Fork 184
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
Check for equality between Fortran and C logicals #692
Conversation
@jvdp1 Yes, sure. I will try in a while and update here. (Now the usable machine is building MPICH which takes forever.) |
@jvdp1 I think that error got fixed with your patch, judging from percentage of the build completed. Now it fails on:
|
UPD. Oops, sorry, it picked wrong GCC. I will rerun with gcc12 now. |
Thank you for confirming it. @awvwgk Could you have a look at the changes and approve them if they are ok for you? Also, there are an issue with MacOS9, but I can't understand what it is.
Ok. I will look at it. |
You do not refer to my reports here, right? Honestly I doubt anyone ever tried to build Fortran
Problem is discussed here: iains/darwin-toolchains-start-here#40 |
Looks like our GCC 9 setup is currently broken. Here is the error message from the workflow:
To me it looks like a too recent version is passed by CMake to the compiler, maybe inferred from |
Nothing beyond Tiger should link to that dylib, I believe. Weird that it is expecting it to be there. |
I'm running the same GCC 9 version on another CI workflow, meson has no problem to use it for compiling Fortran code. Maybe there is an issue with the latest CMake in the compiler detection (wild guess)? |
Having something like this broken for a new macOS would be strange, since it is widely tested and used. But I don’t have ready explanations. |
@awvwgk @barracuda156 I finally implemented @awvwgk 's request. Could you review this PR and merge it, if ok, please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me now. Feel free to merge once we can confirm it fixes the issue.
It does fix the build, and we are already using the patch in Macports: https://github.com/macports/macports-ports/blob/master/lang/fortran-stdlib/files/0001-Check-for-equality-between-Fortran-and-C-logicals.patch |
Addition of CMake rules to check if Fortran and C logicals are equivalent. If so, code will not be compiled for
c_bool
Fixes #691
@barracuda156 Could you test this PR on your computer, please?