Issue with Arduino IDE 2.3.4 on macOS (M1 Pro)

Hi everyone,

I recently downloaded the latest version of Arduino IDE (2.3.4) for macOS. I'm using a MacBook Pro with the following configuration:

Model: MacBook Pro (14-inch, 2021)
Chip: Apple M1 Pro
Memory: 16 GB
macOS Version: Sequoia 15.2

While the installation went smoothly and I was able to set up the necessary packages, I encountered the following error when trying to compile a sketch:

fork/exec /Users/raphaelcomandon/Library/Arduino15/packages/arduino/tools/avr-gcc/7.3.0-atmel3.6.1-arduino7/bin/avr-g++: bad CPU type in executable
Compilation error: fork/exec

/Users/raphaelcomandon/Library/Arduino15/packages/arduino/tools/avr-gcc/7.3.0-atmel3.6.1-arduino7/bin/avr-g++: bad CPU type in executable

It seems like the AVR-GCC toolchain isn't compatible with my architecture. I've already cleared cache files and ensured no remnants of previous installations are interfering.

Could anyone guide me on how to resolve this issue? Do I need to install a specific version of the toolchain for ARM64, or is there a workaround for M1-based Macs?

Thanks in advance for your help!

PS : If you're encountering the same issue, you can resolve it by running this command in the terminal:

softwareupdate --install-rosetta

Thanks to everyone who took the time to read this, and I hope this helps anyone facing the same problem!

PS : If you're encountering the same issue, you can resolve it by running this command in the terminal:

softwareupdate --install-rosetta

Thanks to everyone who took the time to read this, and I hope this helps anyone facing the same problem!

1 Like

Congratulations on finding the solution! I'm glad it is working now. Thank you for taking the time to share your findings. I'm sure the others who have similar problems and find this thread during their research will be very grateful.

The Arduino developers are tracking the task of producing native Apple Silicon builds of the AVR toolchain to avoid the reliance on Rosetta 2 here:

But until that is done, the problem is easily solved by installing Rosetta 2.

Here's how to do it without installing Rosetta.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.