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
Azure DevOps shows GCC 10 compilation errors due to type mismatch between curl_off_t typeof and format #6079
Comments
This confuses me. We've used that formatting for mingw for decades and now suddenly they changed and no longer support that way of printf()ing ? Doesn't it that break like numerous apps? If they changed, shouldn't we then adapt and instead switch mingw builds to use the "classic" printf() formatting? If they didn't change, why does this warn on our code? Isn't this then a mingw/gcc bug? If it's a bug, shouldn't we try to just silence it with |
As I mentioned in #5891 (comment), I do believe this is a compiler bug and we do already suppress this warning. The suppression works in all other places. |
So this log is shown even with |
this build for example, shows this error but rather sets |
With GCC 10 (at least) on mingw, we get false positive warnings when using this option. Never use it for mingw. Fixes #6079
Right, what we do is specifically disable this warning with |
Right, but since it clearly doesn't work here I think we need to level up a little! This take seems to work... |
With GCC 10 (at least) on mingw, we get false positive warnings when using this option. Never use it for mingw. Fixes #6079
Thanks! |
I did this
#5891 tried to fix this previously as I spotted this locally. Now that GCC 10 is also being used in the MSYS2 based Azure DevOps builds, we are bitten by this again in CI:
Logs taken from 32-bit and 64-bit builds of today's release:
The text was updated successfully, but these errors were encountered: