Upgrade rust to 1.10.0 #67
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These fail to build, apparently because some files do not include the appropriate headers, e.g. <mutex> and <condition_variable>
Rust does something fairly different than in 1.7. Instead of just expecting the tarball to exist, it either expects an already extracted and ready toolchain, or else it does everything itself. To work with that, we'll always pass --use-local-rust to ./configure so that bootstrap.py doesn't try to download anything. We'll either download and setup a snapshot ourselves, or use the system rust, based on PACKAGECONFIG[local-rust] as before
Rust 1.10.0 requires the data-layout field This reverts commit d749cbb.
Needed to build under 1.10.0
Needed to build under 1.10.0
The old version no longer builds against the newer libc package
Are you referring to #47? If so, did you try the workaround I commented on here: #47 (comment) ? |
|
Patch looks good to me though. |
This is the compatible version shipped with Rust 1.10.0. Use the git hash from the release TOML file so there is no ambiguity. Update git2 and curl dependencies and patches to match those in Cargo.lock.
cargo: update to 0.11.0
|
rustc native/cross and cargo-native build for me on krogoth. I should point out that Cargo 0.10 does not build with Rust 1.10, and the blessed corresponding Cargo, 0.11, does not build with Rust 1.7. So we have a bisectability issue with cargo-native, but it seems reasonable to me in this case to keep the commits logically separate. Fixes #48 |
ashie
pushed a commit
to webdino/meta-rust
that referenced
this pull request
Nov 23, 2018
…fication chromium: Simplify the M54 recipe.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I had some trouble testing this against poky master due to uninative issues (I had the same problem without my changes). However, I'm able to build rust-native, rust-cross-i586, and several rust packages using poky jethro.