Skip to content

Commit b4c6c8e

Browse files
committed
Clarify that build.full-bootstrap is only used to affect uplifting, not stage selection
1 parent 7a6b50a commit b4c6c8e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

bootstrap.example.toml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -345,9 +345,9 @@
345345
# want to use vendoring. See https://forge.rust-lang.org/infra/other-installation-methods.html#source-code.
346346
#build.vendor = if "is a tarball source" && "vendor" dir exists && ".cargo/config.toml" file exists { true } else { false }
347347

348-
# Typically the build system will build the Rust compiler twice. The second
349-
# compiler, however, will simply use its own libraries to link against. If you
350-
# would rather to perform a full bootstrap, compiling the compiler three times,
348+
# If you build the compiler more than twice (stage3+) or the standard library more than once
349+
# (stage 2+), the third compiler and second library will get uplifted from stage2 and stage1,
350+
# respectively. If you would like to disable this uplifting, and rather perform a full bootstrap,
351351
# then you can set this option to true.
352352
#
353353
# This is only useful for verifying that rustc generates reproducible builds.

0 commit comments

Comments
 (0)