i was planning to do a HelloBoard test program on esp32-c3,but i got this issue,how can i solve this problem. #219
Comments
|
You need a functioning python installation including its package manager pip (which should come by default with any new installation). The I can see from the error log, that it's currently using python from your msys2 installation, which is probably not a good idea, and it doesn't have pip which caused the error. |
|
Sorry, After uninstall MSY2 ，i still can not compile the esp-idf-sys part,This is the log from terminal,i don;t known how to fix it. PS F:\std-training\intro\hardware-check> cargo build warning: Configuring first supported MCU 'esp32c3' derived from the build target 'riscv32imc-esp-espidf' supporting MCUs [esp32c3, esp32c2, esp32h2, esp32c5]; explicitly specify an MCU to resolve this ambiguity error: failed to run custom build command for Caused by: --- stderr CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): CMake Warning at C:/Users/wyx12/.espressif/esp-idf/v4.4.4/tools/cmake/git_submodules.cmake:52 (message): C:\Users\wyx12.espressif\esp-idf\v4.4.4\tools\check_python_dependencies.py:12: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html thread 'main' panicked at ' build script failed, must exit now', C:\Users\wyx12.cargo\registry\src\github.com-1ecc6299db9ec823\cmake-0.1.50\src\lib.rs:1098:5 |
Same error here, any solution? |
|
@Julien-cpsn since the other problem was older, how did you setup your toolchain? also how did you generate the project. Did you go through all steps mention in the esp-rust book https://esp-rs.github.io/book/installation/index.html |
|
@Vollbrecht Hello, thanks for your quick reply Yes I am stuck with an untouched esp idf hello world template that I cannot build. I also did re-do the whole installation process in order to be sure. Here are my system versions:
My rustup targets:
I may be creating another git issue, but let's try here first. The problem I am running into is weird. EDIT: As you may have probably already seen it, it is surely linked to rust-lang/rust#116723 EDIT 2: I don't get the mod wait_status error when rolling back to nightly-2023-10-10-x86_64-pc-windows-msvc, however I am still getting the first error |
|
yeah this problem is the one related to the issue you pointed out and has nothing to do with the initial problem from thes issue. please just use no compiler newer than 2023-10-13 from the nightly branch. You can install every daily nightly rust compiler via |
|
After some check, my error is a little different from @majorzpley's Also, here is my cmake version:
And here is the trace: Sadly, I really don't find where it comes from... |
|
This error you are posting again is another error, its a windows specific error. On windows the path cannot be to long (yeah wtf windows) or it dont work. The only workaround here is to directly user your projects inside a root dir like C:\your-project (trying to make the path as short as possible) or use it inside WSL where you dont have such problems. Windows gonna windows. |
|
Ok thanks man, ima go with the WSL workaround ! Update: building with WSL, flashing with Windows |
PS F:\std-training\intro\hardware-check> cargo run
Compiling esp-idf-sys v0.33.0
Compiling wifi v0.1.0 (F:\std-training\common\lib\wifi)
Compiling rgb-led v0.1.0 (F:\std-training\common\lib\rgb-led)
The following warnings were emitted during compilation:
warning: Configuring first supported MCU 'esp32c3' derived from the build target 'riscv32imc-esp-espidf' supporting MCUs [esp32c3, esp32c2, esp32h2, esp32c5]; explicitly specify an MCU to resolve this ambiguity
error: failed to run custom build command for
esp-idf-sys v0.33.0Caused by:
process didn't exit successfully:
F:\std-training\intro\hardware-check\target\debug\build\esp-idf-sys-95652ea66b616fb0\build-script-build(exit code: 1)--- stdout
cargo:rerun-if-env-changed=ESP_IDF_TOOLS_INSTALL_DIR
cargo:rerun-if-env-changed=ESP_IDF_SDKCONFIG
cargo:rerun-if-env-changed=ESP_IDF_SDKCONFIG_DEFAULTS
cargo:rerun-if-env-changed=MCU
cargo:rerun-if-env-changed=ESP_IDF_SYS_ROOT_CRATE
cargo:rerun-if-env-changed=ESP_IDF_VERSION
cargo:rerun-if-env-changed=ESP_IDF_REPOSITORY
cargo:rerun-if-env-changed=ESP_IDF_CMAKE_GENERATOR
cargo:rerun-if-env-changed=IDF_PATH
cargo:rerun-if-env-changed=EXTRA-COMPONENTS
cargo:rerun-if-env-changed=ESP_IDF_COMPONENTS
cargo:warning=Configuring first supported MCU 'esp32c3' derived from the build target 'riscv32imc-esp-espidf' supporting MCUs [esp32c3, esp32c2, esp32h2, esp32c5]; explicitly specify an MCU to resolve this ambiguity
PATH=C:\Users\wyx12.espressif\esp-idf\v4.4.4\tools;%PATH%
--- stderr
Build configuration: BuildConfig {
esp_idf_tools_install_dir: Some(
Global,
),
esp_idf_sdkconfig: None,
esp_idf_sdkconfig_defaults: Some(
[
"F:\std-training\intro\hardware-check\./sdkconfig.defaults",
],
),
mcu: None,
native: NativeConfig {
esp_idf_version: Some(
Tag(
"v4.4.4",
),
),
esp_idf_repository: None,
esp_idf_cmake_generator: None,
idf_path: None,
extra_components: [],
esp_idf_components: None,
},
esp_idf_sys_root_crate: None,
}
Using managed esp-idf repository: RemoteSdk { repo_url: None, git_ref: Tag("v4.4.4") }
E:\APPS\MSYS2\ucrt64\bin\python.exe: No module named pip
ERROR: Python interpreter at E:\APPS\MSYS2\ucrt64\bin\python.exe doesn't have pip installed. Please check the Getting Started Guides for the steps to install prerequisites for your OS.
Error: Could not install esp-idf
Caused by:
command '"python" "C:\Users\wyx12\.espressif\esp-idf\v4.4.4\tools\idf_tools.py" "--idf-path" "C:\Users\wyx12\.espressif\esp-idf\v4.4.4" "--non-interactive" "install-python-env"' exited with non-zero status code 1
warning: build failed, waiting for other jobs to finish...
The text was updated successfully, but these errors were encountered: