zsh: illegal hardware instruction opencode

[yujianfeikong]

Description

open opencode in Terminal
Error message:
zsh: illegal hardware instruction opencode

Plugins

no

OpenCode version

1.1.19

Steps to reproduce

1.Download the installation package opencode-desktop-darwin-x64.dmg
2. opencode-desktop cannot display content
3. And an error occurs when executing the opencode command in the terminal:
zsh: illegal hardware instruction opencode

Screenshot and/or share link

No response

Operating System

Mac Pro (Late 2013),macOS 12.7.6, Intel Xeon E5,

Terminal

tabby 1.0.229

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Install on Apple M3 Max #256: Install on Apple M3 Max - Reports the same zsh: illegal hardware instruction error on macOS
• Segment failed #3352: Segment failed - Similar illegal instruction error on older hardware (IMac late 2009) with incompatible CPU instructions

Feel free to ignore if none of these address your specific case.

[taazkareem]

I am experiencing this same illegal hardware instruction error on a Mac Pro 6,1 (Late 2013) running macOS Sequoia via OpenCore Legacy Patcher.

The error occurs when the app tries to spawn the opencode-cli sidecar. Manually running the binary confirms the crash:

/Applications/OpenCode.app/Contents/MacOS/opencode-cli serve --port 54328
# Output: zsh: illegal hardware instruction

My CPU (Intel Xeon E5-1650 v2) supports AVX1.0 but lacks AVX2, which appears to be the requirement causing this crash. Here is my sysctl output for reference:

machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC POPCNT AES PCID XSAVE OSXSAVE TSCTMR AVX1.0 RDRAND F16C

Since many Intel Macs (pre-2014) and Xeon-based Mac Pros (pre-2019) are still in use but lack AVX2, would it be possible to provide a baseline (x86-64-v2) build of the CLI sidecar?

[euxaristia]

just caught this bug on the latest version from the yolo curl | bash installer on Raspberry Pi 4 w/ Raspberry Pi OS 13 (Trixie)

[princejeshurun17]

just caught this bug on the latest version from the yolo curl | bash installer on Raspberry Pi 4 w/ Raspberry Pi OS 13 (Trixie)

can confirm, facing the same issue

[euxaristia]

just caught this bug on the latest version from the yolo curl | bash installer on Raspberry Pi 4 w/ Raspberry Pi OS 13 (Trixie)

can confirm, facing the same issue

I managed to fix it by downgrading to 1.1.53(and disabling auto-update!!!) which seems like the last build which doesn't have the new instructions from bunjs, but then trinity large free just started glitching out with tooling anyway, so I decided to stop using open code on my Pi for now because I have other, paid, options and I can't be using a fixed version which is flawed and quickly improving.