-
Notifications
You must be signed in to change notification settings - Fork 17
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
Stop building with -Werror
#81
Conversation
`-Werror` should not be used in default build flags as it makes the compilation fail every time somebody tries to build with a new version of the compiler which triggers a new warning. It should only be set when running CI.
Merge? |
We should add this back on in CI as a part of this PR then. |
I've added a commit which seems like it should have done that, but the logs show that the compiler was called without |
I think flags are overridden at libblastrampoline/test/utils.jl Lines 64 to 68 in b829b0e
|
Thanks, seems to work now! |
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, but I think the setting of cflags can be simplified in tests
Should be good now. |
Side note, I think the warning was fixed by #71, right? |
Thanks, @nalimilan! |
-Werror
should not be used in default build flags as it makes the compilation fail every time somebody tries to build with a new version of the compiler which triggers a new warning. It should only be set when running CI.I saw this when trying to build the RPM for Julia 1.8.0-rc3 on Fedora rawhide (with GCC 12.1.1):
The warning probably deserves some attention but the problem isn't new I guess so there's no reason to worry the particular user who happened to build with a new compiler version.