-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Repoint cc dep in bootstrap to its latest version. #134344
base: master
Are you sure you want to change the base?
Conversation
v1.2.4 handles new/unofficial targets much better than v1.2.0. Also bump cmake's version, as it is linked to cc.
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @jieyouxu (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 (
|
@lasiotus could you link to the relnotes for
in the PR description? That way, (1) I have some clue what these bumps entail and (2) if something regresses, we are more likely to know which changes are responsible. As you may have noticed, we pin these since # Most of the time updating these dependencies requires modifications to the
# bootstrap codebase(e.g., https://github.com/rust-lang/rust/issues/124565);
# otherwise, some targets will fail. That's why these dependencies are explicitly pinned.
Can you elaborate on which targets (please also just include that info in PR description for git archaeology purposes)? @rustbot author |
You know what, let's just see what breaks. @bors r+ rollup=never |
Done. |
FYI, a cc update to 1.2.4 (most likely) was the culprit for a failure here |
Thanks! |
Let's see if it's still a problem. |
Based on the changelog, I believe 1.2.2 is the first release that allows using env vars to pass target parameters to cc crate |
Repoint cc dep in bootstrap to its latest version. v1.2.4 handles new/unofficial targets much better than v1.2.0. More specifically, v1.2.4 allows using env vars to pass target parameters to cc crate, as discussed in rust-lang/cc-rs#1317. With v1.2.0, unofficial targets like [Motor OS](https://github.com/moturus/motor-os) [cannot](moturus/motor-os#18) easily rebase to the current rust-lang and have to stay at an [older version](https://github.com/moturus/rust/tree/motor-os_2024-10-18). Also bump cmake's version from 0.1.48 to 0.1.52, as it is linked to cc. cc-rs changelogs: [1.2.4](https://github.com/rust-lang/cc-rs/blob/main/CHANGELOG.md#121---2024-11-14) [1.2.3](https://github.com/rust-lang/cc-rs/blob/main/CHANGELOG.md#123---2024-12-06) [1.2.2](https://github.com/rust-lang/cc-rs/blob/main/CHANGELOG.md#122---2024-11-29) [1.2.1](https://github.com/rust-lang/cc-rs/blob/main/CHANGELOG.md#121---2024-11-14) cmake changelogs/releases: [0.1.52](https://github.com/rust-lang/cmake-rs/blob/master/CHANGELOG.md#0152---2024-11-25) [0.1.51](https://github.com/rust-lang/cmake-rs/blob/master/CHANGELOG.md#0151---2024-08-15) 0.1.50: not a release [0.1.49](https://github.com/rust-lang/cmake-rs/releases/tag/0.1.49)
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
No, that is not the failure I was expecting. |
Repoint cc dep in bootstrap to its latest version. v1.2.4 handles new/unofficial targets much better than v1.2.0. More specifically, v1.2.4 allows using env vars to pass target parameters to cc crate, as discussed in rust-lang/cc-rs#1317. With v1.2.0, unofficial targets like [Motor OS](https://github.com/moturus/motor-os) [cannot](moturus/motor-os#18) easily rebase to the current rust-lang and have to stay at an [older version](https://github.com/moturus/rust/tree/motor-os_2024-10-18). Also bump cmake's version from 0.1.48 to 0.1.52, as it is linked to cc. cc-rs changelogs: [1.2.4](https://github.com/rust-lang/cc-rs/blob/main/CHANGELOG.md#121---2024-11-14) [1.2.3](https://github.com/rust-lang/cc-rs/blob/main/CHANGELOG.md#123---2024-12-06) [1.2.2](https://github.com/rust-lang/cc-rs/blob/main/CHANGELOG.md#122---2024-11-29) [1.2.1](https://github.com/rust-lang/cc-rs/blob/main/CHANGELOG.md#121---2024-11-14) cmake changelogs/releases: [0.1.52](https://github.com/rust-lang/cmake-rs/blob/master/CHANGELOG.md#0152---2024-11-25) [0.1.51](https://github.com/rust-lang/cmake-rs/blob/master/CHANGELOG.md#0151---2024-08-15) 0.1.50: not a release [0.1.49](https://github.com/rust-lang/cmake-rs/releases/tag/0.1.49)
💔 Test failed - checks-actions |
|
@bors r- |
I'm going to reroll a bootstrap reviewer because I don't currently have the bandwidth to help diagnose a r? bootstrap |
Going to try and look into this today with #134558 |
[EXPERIMENTAL] Bisect cmake bootstrap issue r? `@ghost` Investigating rust-lang#134344 try-job: dist-apple-various
[EXPERIMENTAL] Bisect cmake bootstrap issue r? `@ghost` Investigating rust-lang#134344 try-job: dist-apple-various
[EXPERIMENTAL] Bisect cmake bootstrap issue r? `@ghost` Investigating rust-lang#134344 try-job: dist-apple-various
[EXPERIMENTAL] Bisect cmake bootstrap issue r? `@ghost` Investigating rust-lang#134344 try-job: dist-apple-various
[EXPERIMENTAL] Bisect cmake bootstrap issue r? `@ghost` Investigating rust-lang#134344 try-job: dist-apple-various
[EXPERIMENTAL] Bisect cmake bootstrap issue r? `@ghost` Investigating rust-lang#134344 try-job: dist-apple-various
[EXPERIMENTAL] Bisect cmake bootstrap issue r? `@ghost` Investigating rust-lang#134344 try-job: dist-apple-various
[EXPERIMENTAL] Bisect cmake bootstrap issue r? `@ghost` Investigating rust-lang#134344 try-job: dist-apple-various
[EXPERIMENTAL] Bisect cmake bootstrap issue r? `@ghost` Investigating rust-lang#134344 try-job: dist-apple-various
Details in the PR, but current status is that rust-lang/cmake-rs@d668808 regressed, as we don't provide |
v1.2.4 handles new/unofficial targets much better than v1.2.0.
More specifically, v1.2.4 allows using env vars to pass target parameters to cc crate, as discussed in rust-lang/cc-rs#1317. With v1.2.0, unofficial targets like Motor OS cannot easily rebase to the current rust-lang and have to stay at an older version.
Also bump cmake's version from 0.1.48 to 0.1.52, as it is linked to cc.
cc-rs changelogs:
1.2.4
1.2.3
1.2.2
1.2.1
cmake changelogs/releases:
0.1.52
0.1.51
0.1.50: not a release
0.1.49