-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Avoid the need to "make clean" manually when building Rust #2320
Comments
Do we have a procedure for reproducing this? |
Well, if you check out a version that has 0.2 in the metadata, then make, then check out a version that has 0.3, then make check, the checks fail. Also, make clean does not actually make very clean. I'm filing another bug about that. |
I believe this is still an issue. Often even with just daily pulls from master, I get "multiple matching crates for std" and have to make clean. This isn't a backwards-compatibility issue. Re-nominating for production-ready. |
cc #2419 |
accepted for production ready |
reduce regex features to reduce rebuilds Helps with the issue I [mentioned on Zulip](https://rust-lang.zulipchat.com/#narrow/stream/269128-miri/topic/Miri.20rebuilds/near/287442340).
Sometimes (perhaps when pulling patches, perhaps not), metadata gets out of date and isn't rebuilt automatically. #2318 is just one example. If the build system works properly, ideally it would never be necessary to manually "make clean".
This is confusing for a user since the error message (for example, "nonexhaustive match failure" in #2318) says nothing about how to fix the problem.
The text was updated successfully, but these errors were encountered: