Closed SVH-Powel closed 1 year ago
I read somewhere to try this:
I know, sounds stupid but worked for me, now I can compile my ESP32 nodes again.
I tried to shell into the container and the link trick above was already done properly:
root@bagend:/config# ls -l /lib/ld-linux.so.3
lrwxrwxrwx 1 root root 38 May 17 01:21 /lib/ld-linux.so.3 -> /lib/arm-linux-gnueabihf/ld-linux.so.3
I then looked into disabling my arm64 kernel to see if that would help (also means I will max out at 4GB on my 8GB Pi I guess?), followed this guide and added arm_64bit=0
to the [pi4]
section of /boot/config.txt
and restarting. After a bit of a stressful reboot we are in 32 bit mode:
fred@bagend:~ $ uname -a
Linux bagend 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
Got the ESPHome Docker container up and tried to update one of my nodes, that then downloads a new version of the toolchain and builds / installs no problem.
So that means the issue really is the kernel, and this pretty involved workaround works. I guess I will update all my nodes, and upgrade my system to Raspberry Pi OS 64 bit, however scary that sounds. I can say that this used to work for sure, so something broke recently, either in ESPHome or in the toolchains.
The problem
Compile fails with "sh: 1: xtensa-esp32-elf-g++: not found"
Which version of ESPHome has the issue?
2022.12.0
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2022.12.5
What platform are you using?
ESP32
Board
esp32dev
Component causing the issue
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response