Skip to content

Remove unstable marker from std::rt #17349

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

Merged
merged 1 commit into from
Sep 18, 2014
Merged

Conversation

aturon
Copy link
Member

@aturon aturon commented Sep 17, 2014

The std::rt module was marked unstable a while back, and this change was not reverted when we moved to an experimental baseline for std.

The `std::rt` module was marked `unstable` [a while
back](rust-lang@b6d4d11),
and this change was not reverted when we moved to an `experimental`
baseline for `std`.
@aturon
Copy link
Member Author

aturon commented Sep 17, 2014

@alexcrichton Spurious failure?

@alexcrichton
Copy link
Member

That is an absurd looking error!

Looks like String::from_utf8 failed somewhere, and the translated bytes from the failure message is:

=> "x86_64-unknown-linux-gnu/stage2/bin/rustc \xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF/rust-buildbot/slave/auto-linux-64-opt/build/src/test/compile-fail/lint-group-style.rs -L x86_64-unknown-linux-gnu/test/compile-fail --target=x86_64-unknown-linux-gnu -L x86_64-unknown-linux-gnu/test/compile-fail/lint-group-style.stage2-x86_64-unknown-linux-gnu.libaux -C prefer-dynamic -o x86_64-unknown-linux-gnu/test/compile-fail/lint-group-style.stage2-x86_64-unknown-linux-gnu --cfg rtopt --cfg debug -O -L x86_64-unknown-linux-gnu/rt"

I have no idea where the \xFF is coming from...

bors added a commit that referenced this pull request Sep 18, 2014
The `std::rt` module was marked `unstable` [a while back](b6d4d11), and this change was not reverted when we moved to an `experimental` baseline for `std`.
@bors bors closed this Sep 18, 2014
@bors bors merged commit 4ef9e1e into rust-lang:master Sep 18, 2014
lnicola pushed a commit to lnicola/rust that referenced this pull request Jun 23, 2024
chore: Update Cargo.lock to avoid yanked version

Building rust-analyzer currently generates a warning because libc 0.2.154 has been yanked. Update to 0.2.155 in Cargo.lock.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants