You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Segmentation fault on Chimera Linux (musl libc) due to glibc dependency #17440
I'm trying to run OpenCode on Chimera Linux, which uses musl libc instead of glibc. The binary installs correctly, but it immediately crashes with a segmentation fault when executed.
System information:
OS: Chimera Linux
Kernel: 6.19.2
Architecture: x86_64
Terminal: kitty (xterm-kitty)
Steps to reproduce:
Install OpenCode using the official install script:
Error relocating opencode: gnu_get_libc_version: symbol not found
Error relocating opencode: backtrace: symbol not found
Error relocating opencode: backtrace_symbols: symbol not found
Error relocating opencode: malloc_trim: symbol not found
Error relocating opencode: __cxa_thread_atexit_impl: symbol not found
Error relocating opencode: __cxa_at_quick_exit: symbol not found
Error relocating opencode: __register_atfork: symbol not found
Error relocating opencode: __fprintf_chk: symbol not found
Error relocating opencode: __sprintf_chk: symbol not found
Error relocating opencode: __strftime_l: symbol not found
This seems to indicate the binary is built against glibc and therefore incompatible with musl-based distributions like:
Chimera Linux
Alpine Linux
postmarketOS
Feature request:
It would be very helpful if a musl-compatible build could be provided, for example:
x86_64-unknown-linux-musl
Many modern CLI tools provide both glibc and musl builds to support Alpine/musl ecosystems.
Activity
github-actions commentedon Mar 14, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is the same, please consider adding a "+1" or additional context there instead of opening a new report.
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.