-
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
openmp flag in OSX #32
Comments
@lkreidberg I've had a couple of people now who have not been able to install batman (as a dependency of Mirage on their machines running Mac OSX 10.14. Removing |
for me, it would be much better to activate OpenMP since most modern CPUs are multi-core :) the problem is options is C compilers on OSX are a mess, options are changing, and you need to have a full LLVM to have OpenMP in Clang in recent OSX (eg 10.14). Documentation is unclear or missleading. One of my students, making regression on OSX and C compilers (gcc & clang) on a large code, spend weeks to realize the horrible details & differences between options and effective (or not) activations of OpenMP on OSX 10.12, 10.13 then 10.14. A mess. Often, solutions on Web site are just for a given version of a give compiler & OSX version. Take care. My solution above should be more general. (need a recent Cmake). But not garantee on last OSX. |
Thanks for raising this issue Bryan, and for your comment Alain. Yeah, Alain is right - OpenMP is a huge hassle on OSX! If you don't need parallel processing capability it's fine to just remove the |
We had trouble with batman-package-2.4.6 with OpenMP flag on OSX 10.12 with clang
(on such OSX, gcc is a link to clang, without OpenMP operational ... we do have to deactivate openmp flag. Furthermore, on OSX & clang, the OpenMP flag is -fgomp)
I just add a line after the line 65
and then succeed to go to the end
The text was updated successfully, but these errors were encountered: