-
Notifications
You must be signed in to change notification settings - Fork 13.4k
conflicting types
build failure on mingw-w64 32bit
#10327
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Quick fix is adding I think we should prepare a plan when mingw also fixes it. (They already fixed third one of #9246 on w32api-4.0.3.) |
@klutzy: mingw-w64 gets its' own section in platform.mk, doesn't it? So adding mingw-fix-include to include path in rt.mk can be conditioned on some macro defined there. As for mingw fixing their headers, I think we can just remove fixed headers from mingw-fix-include when that happens. |
@vadimcn I'm building rust on mingw-w64-32bit but rust thinks it is on mingw. I'm not sure this is "legal", but I don't want to cross-build from mingw to mingw-w64-32bit since their difference is small. |
|
…rednet [`match_same_arms`]: don't lint if `non_exhaustive_omitted_patterns` Fixes rust-lang#10327 changelog: [`match_same_arms`]: Don't lint if `non_exhaustive_omitted_patterns` is `warn` or `deny`
Latest mingw has broken headers (#9246) therefore #9254 added missing definitions locally. This causes error on mingw-w64 since its header is not broken. :(
cc @vadimcn
The text was updated successfully, but these errors were encountered: