Uh oh!
There was an error while loading. Please reload this page.
Fix cross compiling dist/build invocations - #76799
Conversation
Mark-Simulacrum
commented
Sep 16, 2020
It looks like the first commit here is presumably either an incomplete fix or something like that, https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/x.2Epy.20calls.20itself.20recursively.3F/near/210307295. |
Otherwise, we may not have a standard library built for the native "host" target of the rustc being run.
This isn't an issue for most folks who use x.py dist, which will directly depend on this. But for x.py build, if we don't properly set target here rustdoc will not be built. Currently, there is not a default-on step for generating a rustc for a given target either, so we will fail to build a rustc as well.
Mark-Simulacrum
commented
Sep 16, 2020
Looks like that was a false alarm -- seems like this is actually fixed (or at least that build is not evidence otherwise). |
glandium
commented
Sep 16, 2020
I can confirm it works, but it also builds a stage1 "host" compiler with |
Mark-Simulacrum
commented
Sep 17, 2020
I think that's probably avoidable but will be a more invasive change so I'll leave it to future work (unless @alexcrichton feels we should do it here). We'll probably need to model compile::Std and other steps similar to how rustdoc is done, where they don't ask for a top_stage compiler which they don't actually need. |
alexcrichton
commented
Sep 17, 2020
Seems reasonable to me, and yeah further optimizations can probably come later. Would it be possible to add a test for this? These sorts of bugs are notoriously hard to protect against otherwise |
3c6cf7e to
363aff0CompareMark-Simulacrum
commented
Sep 17, 2020
Okay @alexcrichton just pushed a test, annotated with a fixme comment since it's over-building things currently |
alexcrichton
commented
Sep 17, 2020
@bors: r+ |
bors
commented
Sep 17, 2020
📌 Commit 363aff0 has been approved by |
…ist, r=alexcrichton Fix cross compiling dist/build invocations I am uncertain why the first commit is not affecting CI. I suspect it's because we pass --disable-docs on most of our cross-compilation builders. The second commit doesn't affect CI because CI runs x.py dist, not x.py build. Both commits are standalone; together they should resolverust-lang#76733. The first commit doesn't really fix that issue but rather just fixes cross-compiled x.py dist, resolving a bug introduced in rust-lang#76549.
…ist, r=alexcrichton Fix cross compiling dist/build invocations I am uncertain why the first commit is not affecting CI. I suspect it's because we pass --disable-docs on most of our cross-compilation builders. The second commit doesn't affect CI because CI runs x.py dist, not x.py build. Both commits are standalone; together they should resolverust-lang#76733. The first commit doesn't really fix that issue but rather just fixes cross-compiled x.py dist, resolving a bug introduced in rust-lang#76549.
…ist, r=alexcrichton Fix cross compiling dist/build invocations I am uncertain why the first commit is not affecting CI. I suspect it's because we pass --disable-docs on most of our cross-compilation builders. The second commit doesn't affect CI because CI runs x.py dist, not x.py build. Both commits are standalone; together they should resolverust-lang#76733. The first commit doesn't really fix that issue but rather just fixes cross-compiled x.py dist, resolving a bug introduced in rust-lang#76549.
…ist, r=alexcrichton Fix cross compiling dist/build invocations I am uncertain why the first commit is not affecting CI. I suspect it's because we pass --disable-docs on most of our cross-compilation builders. The second commit doesn't affect CI because CI runs x.py dist, not x.py build. Both commits are standalone; together they should resolverust-lang#76733. The first commit doesn't really fix that issue but rather just fixes cross-compiled x.py dist, resolving a bug introduced in rust-lang#76549.
…ist, r=alexcrichton Fix cross compiling dist/build invocations I am uncertain why the first commit is not affecting CI. I suspect it's because we pass --disable-docs on most of our cross-compilation builders. The second commit doesn't affect CI because CI runs x.py dist, not x.py build. Both commits are standalone; together they should resolverust-lang#76733. The first commit doesn't really fix that issue but rather just fixes cross-compiled x.py dist, resolving a bug introduced in rust-lang#76549.
ecstatic-morse
commented
Sep 22, 2020
@bors rollup=iffy |
bors
commented
Sep 22, 2020
bors
commented
Sep 22, 2020
☀️ Test successful - checks-actions, checks-azure |
I am uncertain why the first commit is not affecting CI. I suspect it's because we pass --disable-docs on most of our cross-compilation builders. The second commit doesn't affect CI because CI runs x.py dist, not x.py build.
Both commits are standalone; together they should resolve#76733. The first commit doesn't really fix that issue but rather just fixes cross-compiled x.py dist, resolving a bug introduced in #76549.