Help with cargo build fixing /usr/include/limits.h:124:16: fatal error: 'limits.h' file not found

[potto216]

Hi I was wondering if anyone had advice for how to fix the below error

  --- stderr
  /usr/include/limits.h:124:16: fatal error: 'limits.h' file not found
  thread 'main' panicked at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mbedtls-sys-auto-2.28.7/build/bindgen.rs:153:14:
  bindgen error: ClangDiagnostic("/usr/include/limits.h:124:16: fatal error: 'limits.h' file not found\n")
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

which I get from a fresh clone and cargo build using rustc 1.78.0 (9b00956e5 2024-04-29). The VM is Linux matter-dev 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux and I can build and run other matter code on the VM such as chip-tool and matter.js.

When searching for a solution I found the error /usr/include/limits.h:124:16: fatal error: 'limits.h' file not found common for many projects, but the solutions seem to be pretty varied. I also looked at the crate project https://github.com/rust-mbedtls/mbedtls which it seems to be associated with, but could not find any clues. The error is in the limits.h file and assiocated with #include_next <limits.h> shown below:

 /* Get the compiler's limits.h, which defines almost all the ISO constants.
118
119     We put this #include_next outside the double inclusion check because
120     it should be possible to include this file more than once and still get
121     the definitions from gcc's header.  */
122 #if defined __GNUC__ && !defined _GCC_LIMITS_H_
123 /* `_GCC_LIMITS_H_' is what GCC's file defines.  */
124 # include_next <limits.h>
125 #endif
126

The full build logs are here: build_out.txt

Thanks for any help!
Paul

[SilenceMay]

？

[ivmarkov]

Sorry for the delay. I did not even know we are having a Q&A section!

I suggest as a quick workaround to build the lib with either --feature rustcrypto or --feature openssl instead.

While we have to get to the root cause of the mbedtls thing,
a) it has other bugs (somehow has regressed and does not work with Alexa)
b) the mbedtls Rust crate is in maintenance mode, stuck on mbedtls 2.x

[potto216]

Thanks for the reply. I tried cargo build --features rustcrypto and I got the same error, but then I did a git pull and when I rebuilt with just cargo build the error went away. Not sure why, but it now builds:).

In the future should I open an issue for problems like this or use the discussions?

[ivmarkov]

In the future should I open an issue for problems like this or use the discussions?

Doesn't matter anymore, as I'm now subscribed to everything and receive email notifications for everything. :)