Closed
Description
(In this example BUILD = x86_64-unknown-linux-gnu
and HOST=arm-unknown-linux-gnueabi
)
$ x.py build --stage 1 src/rustc --host=$HOST
Building stage0 std artifacts (x86_64-unknown-linux-gnu -> arm-unknown-linux-gnueabi)
(..)
Building stage0 test artifacts (x86_64-unknown-linux-gnu -> arm-unknown-linux-gnueabi)
(..)
Building stage0 compiler artifacts (x86_64-unknown-linux-gnu -> arm-unknown-linux-gnueabi)
(..)
Building stage0 std artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
(..)
Building stage0 test artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
(..)
Building stage0 compiler artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
(..)
Building stage1 std artifacts (x86_64-unknown-linux-gnu -> arm-unknown-linux-gnueabi)
(..)
Building stage1 test artifacts (x86_64-unknown-linux-gnu -> arm-unknown-linux-gnueabi)
(..)
Building stage1 compiler artifacts (x86_64-unknown-linux-gnu -> arm-unknown-linux-gnueabi)
(..)
This part:
Building stage0 std artifacts (x86_64-unknown-linux-gnu -> arm-unknown-linux-gnueabi)
(..)
Building stage0 test artifacts (x86_64-unknown-linux-gnu -> arm-unknown-linux-gnueabi)
(..)
Building stage0 compiler artifacts (x86_64-unknown-linux-gnu -> arm-unknown-linux-gnueabi)
(..)
seems unnecessary as that compiler won't be used in the bootstrap (in fact, it can be executed by the build machine due to the differences in architectures) and it's not the requested rustc either.