Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Mark-Simulacrum (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
|
Thanks! r? jieyouxu |
|
Hang on, need to double-check whats happening with @bors r- |
|
Hm I can't find the other one, so let's see what fails. @bors r+ |
|
I've verified locally that cc >= 1.2.2 breaks our build so |
|
☔ The latest upstream changes (presumably #134425) made this pull request unmergeable. Please resolve the merge conflicts. |
…89,jieyouxu Bump compiler `cc` to 1.2.5 - `cc` 1.2.4 contains a fix to address [rustc uses wrong build tools when compiling from MSVC rust-lang#133794](rust-lang#133794). See <https://github.com/rust-lang/cc-rs/releases/tag/cc-v1.2.4>. - `cc` 1.2.5 contains a fix to also check linking when testing if certain compiler flags are supported, which fixed an issue that was causing previous compiler `cc` bumps to fail. See <https://github.com/rust-lang/cc-rs/releases/tag/cc-v1.2.5>. Supersedes rust-lang#134419. Fixes rust-lang#133794. r? `@clubby789`
This fixes the issue of the wrong build tools being used when cross-compiling from msvc. Fixes #133794.