Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there, following up on #15, I tried updating to the latest nightly and was mostly successful, with some minor hiccups. I was able to run the
build-src.sh
script and interactively apply each patch it gave to me, but at the end of it all it still failed to build, giving theUnknown compiler version, upgrade core_io?
message. It also seemed to me like it didn't give me a whole year's worth of nighties to patch, so I'm wondering if it stopped early for some reason? Here's the output from running the build-src command:This output is after I had already interactively applied the patches. But it seems like there aren't a year's worth of patches here, and I'm also a little confused as to why the commit hashes are in alphabetical order (I'd expect them to be listed chronologically?). I was wondering if you know what's going on with the failure in
build.rs
?Some more background info:
Rustup version:
In my local Rust repository, I've pulled the latest master (
befeeb7c083c9e5edddc86563cc461185d897a13
), which I believe should include the nightly I'm aiming for in its history.