Update new target check-cfg instructions

This commit is contained in:
Urgau 2024-07-01 11:23:58 +02:00 committed by Tshepang Mbambo
parent 98c5f27cf7
commit d6e3a32a55
1 changed files with 11 additions and 5 deletions

View File

@ -86,12 +86,18 @@ unexpected because stage0 doesn't know about the new target specification and
we pass `--check-cfg` in order to tell it to check. we pass `--check-cfg` in order to tell it to check.
To fix the errors you will need to manually add the unexpected value to the To fix the errors you will need to manually add the unexpected value to the
`EXTRA_CHECK_CFGS` list in `src/bootstrap/src/lib.rs`. Here is an example for different `Cargo.toml` in `library/{std,alloc,core}/Cargo.toml`. Here is an
adding `NEW_TARGET_OS` as `target_os`: example for adding `NEW_TARGET_ARCH` as `target_arch`:
*`library/std/Cargo.toml`*:
```diff ```diff
- (Some(Mode::Std), "target_os", Some(&["watchos"])), [lints.rust.unexpected_cfgs]
+ // #[cfg(bootstrap)] NEW_TARGET_OS level = "warn"
+ (Some(Mode::Std), "target_os", Some(&["watchos", "NEW_TARGET_OS"])), check-cfg = [
'cfg(bootstrap)',
- 'cfg(target_arch, values("xtensa"))',
+ # #[cfg(bootstrap)] NEW_TARGET_ARCH
+ 'cfg(target_arch, values("xtensa", "NEW_TARGET_ARCH"))',
``` ```
To use this target in bootstrap, we need to explicitly add the target triple to the `STAGE0_MISSING_TARGETS` To use this target in bootstrap, we need to explicitly add the target triple to the `STAGE0_MISSING_TARGETS`