Repository navigation
Closed
Labels
C-bugCategory: This is a bug.Category: This is a bug.O-muslTarget: The musl libcTarget: The musl libcO-windows-gnuToolchain: GNU, Operating system: WindowsToolchain: GNU, Operating system: WindowsP-highHigh priorityHigh priorityT-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-releaseRelevant to the release subteam, which will review and decide on the PR/issue.Relevant to the release subteam, which will review and decide on the PR/issue.regression-from-stable-to-nightlyPerformance or correctness regression from stable to nightly.Performance or correctness regression from stable to nightly.
Description
$ rustup toolchain add nightly-2019-10-11
$ rustup toolchain add nightly-2019-10-12
$ rustup target add --toolchain nightly-2019-10-11 x86_64-fortanix-unknown-sgx
$ rustup target add --toolchain nightly-2019-10-12 x86_64-fortanix-unknown-sgx
$ ls .rustup/toolchains/nightly-2019-10-11-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-fortanix-unknown-sgx/lib/libunwind.a
.rustup/toolchains/nightly-2019-10-11-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-fortanix-unknown-sgx/lib/libunwind.a
$ ls .rustup/toolchains/nightly-2019-10-12-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-fortanix-unknown-sgx/lib/libunwind.a
ls: cannot access '.rustup/toolchains/nightly-2019-10-12-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-fortanix-unknown-sgx/lib/libunwind.a': No such file or directory
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bug.Category: This is a bug.O-muslTarget: The musl libcTarget: The musl libcO-windows-gnuToolchain: GNU, Operating system: WindowsToolchain: GNU, Operating system: WindowsP-highHigh priorityHigh priorityT-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-releaseRelevant to the release subteam, which will review and decide on the PR/issue.Relevant to the release subteam, which will review and decide on the PR/issue.regression-from-stable-to-nightlyPerformance or correctness regression from stable to nightly.Performance or correctness regression from stable to nightly.
Activity
[-]3rd party libraries missing from nightly-2019-10-12 for target x86_64-fortanix-unknown-sgx[/-][+]3rd party libraries missing from nightly-2019-10-12[/+]jethrogb commentedon Oct 12, 2019
x86_64-unknown-linux-musl is also affected
Checkout the size difference:
Link error when trying to build a musl binary:
[-]3rd party libraries missing from nightly-2019-10-12[/-][+]3rd party objects missing from nightly-2019-10-12[/+]mati865 commentedon Oct 12, 2019
I checked
rust-std,rustcandrustc-devcomponents and libs mentioned above are totally gone.@rustbot modify labels: +T-release +C-bug
mati865 commentedon Oct 12, 2019
Tier-1
windows-gnutoolchain is also broken:emilyalbini commentedon Oct 12, 2019
cc @rust-lang/release
emilyalbini commentedon Oct 12, 2019
So @rust-lang/release, as the
rustc-devPR broke tons of tier 2 targets and even a tier 1 target, I'd say for now we should revert the change and then land it again once it's properly fixed and tested on most of the platforms we support.I think the priority should be keeping nightly as usable as possible (thus reverting the PR), reducing the stdlib size is less important and can be done later.
8 remaining items
gnzlbg commentedon Oct 14, 2019
All
libcmusl build jobs are also failing, probably due to this.cuviper commentedon Oct 14, 2019
Revert #65342 landed 15 hours ago, so the next nightly should have the original full rust-std again. We'll retry the limited set later, with any 3rd party objects needed, but first I want to figure out how to sanity-check the dist package in CI for all targets so this doesn't regress.
There is a
distcheckjob, but only forx86_64-unknown-linux-gnu, which wasn't affected. On Discord we were talking about adding a simple "hello world" test as something quick for all targets.emilyalbini commentedon Oct 15, 2019
This should be fixed in the latest nightly.
jethrogb commentedon Oct 15, 2019
Yup it is!