-
Notifications
You must be signed in to change notification settings - Fork 19
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
-std=c++11
breaks clang
builds
#78
Comments
See this diff for a potential fix:
|
I don’t think this will work, because you need the |
Or maybe you don't need the flag currently, although eventually you might need it. It's been a while since I opened this issue and haven't checked recently. |
The builds on conda-forge worked just fine. |
the default in clang is past c++11 now |
Yes, it does seem to work to just not set the Checking |
Confirmed: commenting line |
I'm happy to take a PR on this |
where are we on this? |
I can take a look and see whether I can fix this quickly. Still having the issue locally... |
The fix from #75 breaks the build process on Macs with clang (the default compiler), because clang doesn't allow the
-std=c++11
flag when compiling C code. So ideally, you'd only want to have this flag on for the*.cpp
files, but not for the*.c
files. However, this seems quite difficult to do, asdistutils
tries hard to use the same flags for all files. The easiest solution might just be to make this an optional flag that can be turned off or detecting that this flag doesn't work and turning it off automatically. Note that the current way of checking the compiler flags doesn't detect this issue, because it compiles a C++ file and for that the flag is fine. You could do the check with a C file, but I'm not sure that that doesn't lead to other issues.The text was updated successfully, but these errors were encountered: