From 5e4e8da4851b92c18f31df0c63f075219ad4e5ff Mon Sep 17 00:00:00 2001 From: Martin Nordholts Date: Thu, 26 Mar 2026 19:39:05 +0100 Subject: [PATCH] bootstrap.example.toml: Hint how to allow `build.warnings` This commit turns "Actual" into "Expected" for the following problem: Steps: 1. Do some quick and experimental local code changes in the compiler code. 2. Run `./x build`. 3. Observe `error: warnings are denied by `build.warnings` configuration`. 4. Decide to not care and want to allow warnings. 5. Search for `build.warnings` in **bootstrap.example.toml** Actual: No hits. You get frustrated because didn't learn how to allow warnings. Expected: You get a hit and can easily see how to allow warnings. --- bootstrap.example.toml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/bootstrap.example.toml b/bootstrap.example.toml index f3b2a64df853..25e2ca5948bf 100644 --- a/bootstrap.example.toml +++ b/bootstrap.example.toml @@ -826,7 +826,8 @@ # in the sysroot. It is required for running nvptx tests. #rust.llvm-bitcode-linker = false -# Whether to deny warnings in crates +# Whether to deny warnings in crates. Set to `false` to avoid +# error: warnings are denied by `build.warnings` configuration #rust.deny-warnings = true # Print backtrace on internal compiler errors during bootstrap