-
Notifications
You must be signed in to change notification settings - Fork 43
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
Too many default CXXFLAGS #96
Comments
Why do you say that? The language is largely backwards compatible and always has been. Yes I have set them on purpose so that software without complex build systems will take advantage of it without any effort on their part beyond:
.. if c++17 causes an issue then mask that flag out in your |
I did mask it out, and it was indeed the cause of the build failures.
It seems odd to me to switch an opt-in feature to an opt-out feature when there's apparently little to no benefit in doing so, and opting out involves sed while opting in is simple.
I guess C++17 is one such event, then. |
The issue is that the benefits are silently lost if you require opting in and I don't want to lose those. |
Since ctng-compilers inherit
@CXXFLAGS
apparently from build-time of the recipe, activating these compilers sets a lot of flags by default:In particular, setting the
-std
flag seems like an unexpected default behavior for a compiler, to me. Are all of these flags set on purpose, and is there a negative consequence to setting any of these by default? I'm debugging a build issue on nodejs right now, and my first hunch is that it may have to do with the fact that it has two flags for-std
:-std=c++17 -std=gnu++1y
.The text was updated successfully, but these errors were encountered: