Skip to content

Commit e680bb4

Browse files
committed
how-to-build-and-run.md: update "building compiler" section
1 parent 25a5a4f commit e680bb4

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

src/building/how-to-build-and-run.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -226,16 +226,17 @@ Once you've created a `bootstrap.toml`, you are now ready to run
226226
`x`. There are a lot of options here, but let's start with what is
227227
probably the best "go to" command for building a local compiler:
228228

229-
```bash
230-
./x build library
229+
```console
230+
./x build rustc
231231
```
232232

233-
This may *look* like it only builds the standard library, but that is not the case.
234-
What this command does is the following:
233+
What this command does is build `rustc` using the stage0 compiler and stage0 `std`.
234+
235+
To build `rustc` with the in-tree `std`, use this command instead:
235236

236-
- Build `rustc` using the stage0 compiler
237-
- This produces the stage1 compiler
238-
- Build `std` using the stage1 compiler
237+
```console
238+
./x build rustc --stage 2
239+
```
239240

240241
This final product (stage1 compiler + libs built using that compiler)
241242
is what you need to build other Rust programs (unless you use `#![no_std]` or
@@ -253,7 +254,7 @@ signature of some function, you can use `./x check` instead for a much faster bu
253254

254255
Note that this whole command just gives you a subset of the full `rustc`
255256
build. The **full** `rustc` build (what you get with `./x build
256-
--stage 2 compiler/rustc`) has quite a few more steps:
257+
--stage 2 rustc`) has quite a few more steps:
257258

258259
- Build `rustc` with the stage1 compiler.
259260
- The resulting compiler here is called the "stage2" compiler, which uses stage1 std from the previous command.

0 commit comments

Comments
 (0)