Skip to content

Commit eb82984

Browse files
kim-emclaude
andauthored
doc: clarify how to trigger automatic stage0 updates (#11413)
This PR clarifies the bootstrap documentation to explain that to trigger the automatic stage0 update mechanism, you should modify `stage0/src/stdlib_flags.h` (not `src/stdlib_flags.h`). The existing text was ambiguous about which file to modify. 🤖 Prepared with Claude Code Co-authored-by: Claude <[email protected]>
1 parent dc5abb0 commit eb82984

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

doc/dev/bootstrap.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,9 @@ update the archived C source code of the stage 0 compiler in `stage0/src`.
7272

7373
The github repository will automatically update stage0 on `master` once
7474
`src/stdlib_flags.h` and `stage0/src/stdlib_flags.h` are out of sync.
75+
To trigger this, modify `stage0/src/stdlib_flags.h` (e.g., by adding or changing
76+
a comment). When `update-stage0` runs, it will overwrite `stage0/src/stdlib_flags.h`
77+
with the contents of `src/stdlib_flags.h`, bringing them back in sync.
7578

7679
NOTE: A full rebuild of stage 1 will only be triggered when the *committed* contents of `stage0/` are changed.
7780
Thus if you change files in it manually instead of through `update-stage0-commit` (see below) or fetching updates from git, you either need to commit those changes first or run `make -C build/release clean-stdlib`.

0 commit comments

Comments
 (0)