Add remark on required free disk space (#2073)
This commit is contained in:
parent
a8a77cbee1
commit
48bf61ffcd
|
|
@ -367,4 +367,18 @@ everything up then you only need to run one command!
|
||||||
`rm -rf build` works too, but then you have to rebuild LLVM, which can take
|
`rm -rf build` works too, but then you have to rebuild LLVM, which can take
|
||||||
a long time even on fast computers.
|
a long time even on fast computers.
|
||||||
|
|
||||||
|
## Remarks on disk space
|
||||||
|
|
||||||
|
Building the compiler (especially if beyond stage 1) can require significant amounts of free disk
|
||||||
|
space, possibly around 100GB. This is compounded if you have a separate build directory for
|
||||||
|
rust-analyzer (e.g. `build-rust-analyzer`). This is easy to hit with dev-desktops which have a [set
|
||||||
|
disk
|
||||||
|
quota](https://github.com/rust-lang/simpleinfra/blob/8a59e4faeb75a09b072671c74a7cb70160ebef50/ansible/roles/dev-desktop/defaults/main.yml#L7)
|
||||||
|
for each user, but this also applies to local development as well. Occassionally, you may need to:
|
||||||
|
|
||||||
|
- Remove `build/` directory.
|
||||||
|
- Remove `build-rust-analyzer/` directory (if you have a separate rust-analyzer build directory)
|
||||||
|
- Uninstall unnecessary toolchains if you use `cargo-bisect-rustc`. You can check which toolchains
|
||||||
|
are installed with `rustup toolchain list`.
|
||||||
|
|
||||||
[^1]: issue[#1707](https://github.com/rust-lang/rustc-dev-guide/issues/1707)
|
[^1]: issue[#1707](https://github.com/rust-lang/rustc-dev-guide/issues/1707)
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue