search

playfulFence / esp-clock

Implementation of clock on ESP chips and Rust(std). Will be re-implemented as a facility monitoring system on bare-metal Rust
Apache License 2.0
15 stars 3 forks source link

check fail #4

Open ds2k5 opened 2 days ago

ds2k5 commented 2 days ago

Hi, did update the Cargo.toml but cargo check failed...

  1. git clone https://github.com/playfulFence/esp-clock
  2. cd esp-clock
  3. update the Cargo.toml
  4. . ~/export-esp.sh
  5. cargo check

  Checking embedded-svc v0.24.0
error[E0308]: mismatched types
  --> /home/developer/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-idf-sys-0.35.0/src/lib.rs:63:62
   |
63 | const ESP_IDF_TIME64_CHECK: ::std::os::espidf::raw::time_t = 0 as crate::time_t;
   |                                                              ^^^^^^^^^^^^^^^^^^ expected `i32`, found `i64`

error[E0308]: mismatched types
  --> /home/developer/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-idf-sys-0.35.0/src/lib.rs:65:51
   |
65 | const ESP_IDF_TIME64_CHECK_LIBC: ::libc::time_t = 0 as crate::time_t;
   |                                                   ^^^^^^^^^^^^^^^^^^ expected `i32`, found `i64`

For more information about this error, try `rustc --explain E0308`.
The following warnings were emitted during compilation:

warning: esp-idf-sys@0.35.0: Configuring first supported MCU 'esp32c3' derived from the build target 'riscv32imc-esp-espidf' supporting MCUs [esp32c3, esp32c2]; explicitly specify an MCU to resolve this ambiguity

error: could not compile `esp-idf-sys` (lib) due to 2 previous errors

What did I wrong ?

ds2k5 commented 2 days ago

toml.zip