Skip to content
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

Compile failure for ESP-C3 with complaint about as.exe not existing #111

Closed
lonerzzz opened this issue Jan 26, 2025 · 3 comments
Closed
Labels
bug Something isn't working fix-pending fix will be applied in new release Windows issue Issue is caused from Windows

Comments

@lonerzzz
Copy link

I am hitting the following compile error when specifically building for esp32-c3.

riscv32-esp-elf-g++: fatal error: cannot execute 'E:/Prog_Files/Prog/platformio/packages/toolchain-riscv32-esp/bin/../lib/gcc/riscv32-esp-elf/13.2.0/../../../../riscv32-esp-elf/bin/as.exe': CreateProcess: No such file or directory
compilation terminated.
*** [.pio\build\esp32-c3-devkitm-1\src\Log.cpp.o] Error 1
riscv32-esp-elf-g++: fatal error: cannot execute 'E:/Prog_Files/Prog/platformio/packages/toolchain-riscv32-esp/bin/../lib/gcc/riscv32-esp-elf/13.2.0/../../../../riscv32-esp-elf/bin/as.exe': CreateProcess: No such file or directory
compilation terminated.
*** [.pio\build\esp32-c3-devkitm-1\src\Configuration.cpp.o] Error 1
riscv32-esp-elf-g++: fatal error: cannot execute 'E:/Prog_Files/Prog/platformio/packages/toolchain-riscv32-esp/bin/../lib/gcc/riscv32-esp-elf/13.2.0/../../../../riscv32-esp-elf/bin/as.exe': CreateProcess: No such file or directory
compilation terminated.
riscv32-esp-elf-g++: fatal error: cannot execute 'E:/Prog_Files/Prog/platformio/packages/toolchain-riscv32-esp/bin/../lib/gcc/riscv32-esp-elf/13.2.0/../../../../riscv32-esp-elf/bin/as.exe': CreateProcess: No such file or directory
compilation terminated.

My platform.io looks as follows:

[env:esp32-c3-devkitm-1]
;platform = [email protected]
platform = https://github.com/pioarduino/platform-espressif32/releases/download/stable/platform-espressif32.zip
board = esp32-c3-devkitm-1

For tasmota, the discussion indicated that a fix was implemented because of path length issue on windows so I am wondering if the same issue/work around is needed here.
Compile of Tasmota 14.x.x fails for ESP32-Cx

@lonerzzz lonerzzz changed the title Compile failure Compile failure for ESP-C3 with complaint about as.exe not existing Jan 26, 2025
@Jason2866
Copy link

The include shorten path length by using a prefix is not in any release version. The fix for Windows was done after the last release. It is in branch develop. Can be used with

[env:development]
platform = https://github.com/pioarduino/platform-espressif32.git#develop
board = ...
...

@Jason2866 Jason2866 added bug Something isn't working Windows issue Issue is caused from Windows fix-pending fix will be applied in new release labels Jan 26, 2025
@rpannekoek
Copy link

Great to hear that there will be (or kind of is) a fix for this issue on this (great) PlatformIO fork too!
However, for visibility, I would keep the issue open until the fix went into an "official" release.
I encounter this same issue with release 53.03.11 (specifically for C3), whereas it didn't happen with 51.03.07.
I've spent quite some time trying in-between releases (53.03.10 has same problem), going through discussions on Tasmota, trying several of the suggested work-arounds and figuring out what goes wrong with invoking as.exe, exactly (the problem is not that as.exe doesn't exist or that the path to as.exe is too long).
When I wanted to create an issue on this repo with my findings and double-checked whether such an issue wasn't already created in the meantime, I discovered this closed issue.

@Jason2866
Copy link

reopen until fix is in release as suggested from @rpannekoek

@Jason2866 Jason2866 reopened this Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fix-pending fix will be applied in new release Windows issue Issue is caused from Windows
Projects
None yet
Development

No branches or pull requests

3 participants