From c74f970ae328d7eea6b0ead6312fc36249ee92ee Mon Sep 17 00:00:00 2001 From: Joshua Nelson Date: Fri, 1 Jan 2021 15:59:23 -0500 Subject: [PATCH] Clarify that `check` uses a different stage than `build` (#999) --- src/building/bootstrapping.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/building/bootstrapping.md b/src/building/bootstrapping.md index 1d420a97..3e5cabbe 100644 --- a/src/building/bootstrapping.md +++ b/src/building/bootstrapping.md @@ -62,6 +62,7 @@ the `stage1` compiler: `x.py build library/std`. `x.py` tries to be helpful and pick the stage you most likely meant for each subcommand. These defaults are as follows: +- `check`: `--stage 0` - `doc`: `--stage 0` - `build`: `--stage 1` - `test`: `--stage 1` @@ -69,10 +70,13 @@ These defaults are as follows: - `install`: `--stage 2` - `bench`: `--stage 2` -You can always override the stage by passing `--stage N` explicitly. +You can always override the stage by passing `--stage N` explicitly, except for `check`, +which is [hard-coded to stage 0][stage1-check]. For more information about stages, [see below](#understanding-stages-of-bootstrap). +[stage1-check]: https://github.com/rust-lang/rust/issues/46955 + ## Complications of bootstrapping Since the build system uses the current beta compiler to build the stage-1