-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when building on Linux aarch64 #14
Comments
@skerkour I'm afraid that ESP-IDF Tools are not available for Linux - aarch64 - see this issue: espressif/esp-idf#6475 |
@georgik Thank you! Can we keep this issue open so future people with this problem will be able to found it easily? Also I will try to hack my way around by compiling the toolchain myself or something so I may post my progress here. |
Sure. It makes sense to keep it as open. I'll add it as discussion point for next community meeting: esp-rs/rust#80 |
@JurajSadel Steps:
|
I installed the Rust tool-chain last night, as I saw their was an update. It was a fresh install on windows 11 running in a ubuntu docker container, as per the instructions. I understand the test-rust-toolchain.sh is not yet working for the version 4.3 as I am getting an error there. Also I haven't plugged the board in yet, but I noticed that file doesn't have the S3 target in there either. I'm pretty sure the version of IDF I have installed is 4.4 but its calling 4.3 I didn't notice that mentioned in the .sh file. Should I just disregard the test-rust-toolchain.sh? And just try build a project I have for arm64, with the esp32-s3 target? the ulp_gcc is working now, or is it still under development? |
Hello @RepRapid! The default ESP-IDF version that At this moment, |
Hello,
When trying to build on Linux aarch64 (Raspberry pi 4) I got the following error:
Then:
So I successfully hacked my way by manually modifying
platforms/espressif32/platform.py
to requiretoolchain-xtensa32 @ 2.50200.97
instead oftoolchain-xtensa32 @ 2.80400.0
But then I got the following error:
And can't find a solution for this error.
Any idea?
The text was updated successfully, but these errors were encountered: