-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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.42.0 can't compile Rust 1.42.0 #69953
Comments
That change can also be found in 31dcdc9#diff-6710e3160b86e8cc371d2ff58ae1061c, part of the PR when the master branch updated bootstrap to 1.42-beta. |
Hm, I wonder if we should disable deny-warnings by default if we're not in a git repository or so -- in practice I think it's true there's nothing we could have done to prevent this? i.e., rust-lang/rust needs the parens gone to be able to bootstrap. |
I'd still like to see something like distcheck for this -- e.g. use the result of a build as the stage0 of a new build. Even just |
Yes, I think it's true that we could catch this -- I'm less concerned about the "how to know this will happen," but more concerned about the fact that keeping code around to support self-bootstrap may not be viable in all cases (e.g., we used to and perhaps still use bootstrap libtest in compiletest or something like that). OTOH, I believe it is true that such a check would push us to make sure that we bootstrap appropriately which should also always be possible. |
A similar issue has already been discussed previously: Either way, the linked patch fixes the (trivial) issue. Rust 1.42.0 compiles all the crates I've stored locally, good job with the release! |
#68019 switched that to in-tree libtest, but lang differences still apply, like this paren warning. @thomasjfox yeah, I thought I had suggested such a distcheck before... just need someone to get around to it, I guess, assuming we have a little bit of CI budget for the task. |
1.42.0 compiles 1.42.0 just fine here if |
FWIW we set |
Closing since 1.43 is now released and there's a workaround if you still need to build 1.42 |
Hello together,
compiling Rust 1.42.0 with Rust 1.42.0 results in this error early on:
I'm now going to test this fix:
5f979e9#diff-6710e3160b86e8cc371d2ff58ae1061c
The compiler was built with Rust 1.41.1.
I always do the "Rustception" test ;)
The text was updated successfully, but these errors were encountered: