esp8266/Arduino

xtensa-lx106-elf-g++: bad CPU type in executable on a M2 Mac without rosetta emulation installed

Open

#8,725 opened on 2022年11月23日

GitHub で見る
 (4 comments) (0 reactions) (0 assignees)C++ (15,728 stars) (13,342 forks)batch import
help wantedtype: enhancement

説明

I'm trying to compile and upload a sketch to a NodeMCU Lolin V3 board using arduino-cli_0.29.0_macOS_ARM64 but I get the following error whenever I try to compile:

alessio@AleMacBookPro Tools % ./arduino-cli compile --fqbn esp8266:esp8266:nodemcuv2 example



Used platform   Version Path                                                                    
esp8266:esp8266 3.0.2   /Users/alessio/Library/Arduino15/packages/esp8266/hardware/esp8266/3.0.2

Error during build: fork/exec /Users/alessio/Library/Arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.4-gcc10.3-1757bed/bin/xtensa-lx106-elf-g++: bad CPU type in executable

Looks clear that the executable file xtensa-lx106-elf-g++ has been built for x86-64 Mac instead of AMR64... How can I download the correct files for my architecture?

I have been following this procedure, the problem is that arduino-cli core install esp8266:esp8266 downloads the wrong architecture executables, it should download executables built for ARM64 instead of those for x86-64.

コントリビューターガイド

技術スタック
cpp
領域
tooling
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
needs maintainer response
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
knowledge of toolchain compilationARM64 architecture basics
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
20
調査方針
The issue is that the xtensa lx106 elf g++ binary is x86-64 only, causing errors on ARM64 Macs. To resolve, investigate the repository's toolchain build scripts (likely in the 'tools' directory) to see how binaries are built and distributed. Consider adding ARM64 builds or providing instructions for using Rosetta. The maintainers have not yet responded, so a proposed solution involving cross compilation or packaging would be needed.