-
Notifications
You must be signed in to change notification settings - Fork 16
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
MacOS 11.15: error: invalid argument '-std=c++11' not allowed with 'C' #69
Comments
Slight Update number 2I reverted the below changes and instead specified that cmake should use gcc and not clang like so: New command:
Old Command:
This has removed the old error, although I'm still getting the following (after running
Slight update (now out of date)I changed line 10 in New version (note the lack of
Old version (note the inclusion of
I will close this once I've built successfully. |
Due to the issues it seemed to be having with ODE, I did:
After this, the file
And once again I had some issues:
At this point it seems to get past where it was having trouble last time, although still not building properly. I've got no clue what |
So I had a typo, and the parameter that was being passed to
Which doesn't work, but at least now I know I'm using gcc and not clang. With regards to the
This github comment recommends I add some flags to the cxx compiler via this addition to 'the cmake file':
Which resulted in a load of output that looked like an error relating to the program
I'm not sure what to do about this error. The
which I also tried setting (just the LDFLAGS, CPPFLAGS, and PATH changes) but that resulted in the same massive error message, also ending with complaints about x86_64:
I'm not sure what to do now. |
Nice.
After following the instructions on the docs for compiling from source (I'm looking to contribute) on MacOS, everything was good until the compilation step where I was asked to run:
cmake
runs fine, butmake -j3
gives the following error:I'm not sure where the argument (
-std=c++11
) was passed in nor how to solve this issue, although I think it's similar to these:Thanks for any help you can provide!
The text was updated successfully, but these errors were encountered: