-
-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
rust-1.47 contains mismatched tools #63202
Comments
I see the same result, but we're not doing anything special in the build. What does it say after you install it using |
It's not done building, yet, but I can see what's wrong already from the output I've seen so far. The source for cargo is fetched separately, and it's grabbing the wrong cargo tag.
According to Rust's release documentation at https://github.com/rust-lang/rust-forge/blob/master/src/release/process.md the cargo tag that matches to the rustc version is 1 higher, so it should be grabbing 0.48.0 From the instructions for their release folks:
|
No, because the rustc bootstrap is the version before. So rustc is 1.46.0 |
But it's grabbing 1.47.0 for rustc, too:
Looks like you can find the matching cargo version number in src/stage0.txt https://github.com/rust-lang/rust/blob/beta/src/stage0.txt#L17 |
It should be https://github.com/rust-lang/rust/blob/1.47.0/src/stage0.txt#L17 actually, since that's the version we're building. And I believe that rustc 1.46.0 is part of the |
Build finished finally (that sure took a while).
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Now that rust 1.48.0 is out, maybe we could get a fresh build and see if that fixes the issue? |
Oh I see #65286 is in progress, but needs help. |
This will be fixed in #66285, if I can fix the CI errors. Assistance would be appreciated.
|
Unless I've grossly misjudged the impact of the changes I've made in the PR linked above, there are three formulae that are preventing Rust 1.48 (and the fix to this issue) from passing CI:
|
|
Yes. This issue can be closed as well, I believe:
|
Bug report
Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.
brew update
and can still reproduce the problem?brew doctor
, fixed all issues and can still reproduce the problem?brew gist-logs <formula>
(where<formula>
is the name of the formula that failed) and included the output link?brew gist-logs
didn't work: ranbrew config
andbrew doctor
and included their output with your issue?What you were trying to do (and why)
Trying to build Firefox nightly, which now requires Rust 1.47
What happened (include command output)
configure fails complaining that cargo isn't new enough, and requires version 1.47
Command output
What you expected to happen
The utilities installed with rust are supposed to be version-locked to rust itself. If I use rustup-init to install rust instead of using the homebrew package, I get matched versions, which implies something wasn't built right in the package (I can't guarantee that, but that's what it looks like)
Step-by-step reproduction instructions (by running
brew install
commands)The text was updated successfully, but these errors were encountered: