Skip to content

Commit 85a9a43

Browse files
committed
Auto merge of #1612 - camelid:patch-1, r=RalfJung
CONTRIBUTING.md: Use `build --stage 1` instead of `build --stage 2` It seems to work fine with `--stage 1` and it should be faster. Cc #1610 Cc `@jyn514`
2 parents a5c2211 + 6a475c3 commit 85a9a43

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

CONTRIBUTING.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -142,20 +142,20 @@ tracing) enabled.
142142
The setup for a local rustc works as follows:
143143
```sh
144144
# Clone the rust-lang/rust repo.
145-
git clone https://github.com/rust-lang/rust/ rustc
145+
git clone https://github.com/rust-lang/rust rustc
146146
cd rustc
147147
cp config.toml.example config.toml
148148
# Now edit `config.toml` and set `debug-assertions = true`.
149149

150-
# Build a stage 2 rustc.
150+
# Build a stage 1 rustc, and build the rustc libraries with that rustc.
151151
# This step can take 30 minutes or more.
152-
./x.py build --stage 2 compiler/rustc
152+
./x.py build --stage 1 compiler/rustc
153153
# If you change something, you can get a faster rebuild by doing
154-
./x.py build --keep-stage 0 --stage 2 compiler/rustc
154+
./x.py build --keep-stage 0 --stage 1 compiler/rustc
155155
# You may have to change the architecture in the next command
156-
rustup toolchain link custom build/x86_64-unknown-linux-gnu/stage2
156+
rustup toolchain link stage1 build/x86_64-unknown-linux-gnu/stage1
157157
# Now cd to your Miri directory, then configure rustup
158-
rustup override set custom
158+
rustup override set stage1
159159
```
160160

161161
With this, you should now have a working development setup! See

0 commit comments

Comments
 (0)