Building from docker container yield "error: cannot find a built-in macro with name contracts_ensures"

[MihaMarkic]

I've created a VS Code project in a dev container (esp32_latest), created, run cargo generate esp-rs/esp-idf-template cargo and then cargo build only to get the error(s) below.
Am I missing something obvious? Not en expert in rust.

error[E0093]: unrecognized intrinsic function: `contract_check_ensures`
    --> /home/esp/.rustup/toolchains/esp/lib/rustlib/src/rust/library/core/src/intrinsics/mod.rs:4107:8
     |
4107 | pub fn contract_check_ensures<'a, Ret, C: Fn(&'a Ret) -> bool>(ret: &'a Ret, cond: C) {
     |        ^^^^^^^^^^^^^^^^^^^^^^ unrecognized intrinsic
     |
     = help: if you're adding an intrinsic, be sure to update `check_intrinsic_type`

[MihaMarkic]

Here is another one

error[E0522]: definition of an unknown lang item: `RangeInclusiveCopy`
   --> /home/esp/.rustup/toolchains/esp/lib/rustlib/src/rust/library/core/src/range.rs:219:28

[MihaMarkic]

And it starts with this:

...
Downloaded 11 crates (2.1 MB) in 0.41s
  Compiling compiler_builtins v0.1.146
  Compiling core v0.0.0 (/home/esp/.rustup/toolchains/esp/lib/rustlib/src/rust/library/core)
error: cannot find a built-in macro with name `contracts_ensures`
   --> /home/esp/.rustup/toolchains/esp/lib/rustlib/src/rust/library/core/src/macros/mod.rs:1789:5
    |
1789 | /     pub macro contracts_ensures($item:item) {
1790 | |         /* compiler built-in */
1791 | |     }
    | |_____^

[ivmarkov]

The docker container you are using contains a broken rustc version (@SergioGasquez would you agree?).

Until this is fixed, you might want to try installing all prerequisites directly on your machine. These are well described, step-by-step in the esp-idf-template README. The dockerless way would also allow you to dynamically change rustc versions if you again hit a problem.

[Vollbrecht]

@ivmarkov no the devcontainer is not broken, it takes everything latest and still works. At least on my debian machine, and i think OP was also yesterday in Matrix and also got it to work on a fedora machine. It seams though that for whatever reason it gave him hell on a Mac ..

[MihaMarkic]

True that. I've managed to make it work in a (podman) container on Fedora, not sure what went wrong on (podman) Mac. I just retried doing the same as I did with fedora and it still fails. Insert shrug emoticon here.

[MihaMarkic]

Here if it helps (within container on mac)

rustc +esp -v --version
rustc 1.85.0-nightly (fc08bef7e 2025-02-18) (1.86.0.0)
binary: rustc
commit-hash: fc08bef7ed8528e4aed2307195529c55fef62f38
commit-date: 2025-02-18
host: aarch64-unknown-linux-gnu
release: 1.85.0-nightly
LLVM version: 19.1.2

[MihaMarkic]

Container on fedora (x64) - rustc seems newer. I guess macos container is incorrectly built as @ivmarkov suggested.

rustc +esp -v --version
rustc 1.86.0-nightly (5944fc5cd 2025-04-01) (1.86.0.0)
binary: rustc
commit-hash: 5944fc5cd231b5aaf09b471def70ecefefa4737d
commit-date: 2025-04-01
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.2

[ivmarkov]

Yes. This is a wrongly built/updated rustc:

rustc 1.85.0-nightly (fc08bef7e 2025-02-18) (1.86.0.0)

[SergioGasquez]

Xtensa Rust 1.87.0.0 was recently marked as latest, which is what the devcontainer install, I think if you clean and rebuild the devcontainer, it should work

[MihaMarkic]

This guy https://github.com/esp-rs/rust-build/? idf-rust.Containerfile ?
I'll first try pulling new repo and see how it goes.

[MihaMarkic]

Works now fine.

rustc +esp -v --version
rustc 1.87.0-nightly (1dc879ca2 2025-05-27) (1.87.0.0)
binary: rustc
commit-hash: 1dc879ca2c0d9f2afe096cf2ac55c21b503ae967
commit-date: 2025-05-27
host: aarch64-unknown-linux-gnu
release: 1.87.0-nightly
LLVM version: 19.1.2