[BUG] Installer picks musl build on glibc systems (re #14537); musl 2.1.181 now hard-fails with statx: symbol not found on Ubuntu 24.04 LTS

Open 💬 1 comment Opened Jun 18, 2026 by Synthace-Alex-Lewis

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

$ pwd
/home/user/.local/share/claude/versions
$ ./2.1.181 --version
Error relocating ./2.1.181: statx: symbol not found

Summary

On a glibc system that happens to have musl cross-compilation packages installed, the native installer selects the musl build instead of glibc. This is the same root cause as #14537 (closed as not planned / stale). I'm filing fresh because it still reproduces on 2.1.181, and it's now strictly worse: the musl build imports statx, which requires musl ≥ 1.2.5 — newer than any current Debian/Ubuntu stable repo ships — so the mis-selected binary fails to start at all.

Environment

  • OS: Ubuntu 24.04.4 LTS (WSL2)
  • Primary libc: glibc 2.39 (ldd /bin/ls/lib/x86_64-linux-gnu/libc.so.6)
  • musl present only via cross-compile packages: musl 1.2.4-2, musl-dev, musl-tools

(creates /lib/libc.musl-x86_64.so.1)

  • Claude Code: 2.1.181 (broken), 2.1.179 (works)

What Should Happen?

Claude 2.1.181 launches.

Error Messages/Logs

Error relocating /home/user/.local/bin/claude: statx: symbol not found
Error relocating ./2.1.181: statx: symbol not found

Steps to Reproduce

on a glibc Ubuntu system

sudo apt install -y musl musl-dev musl-tools # creates /lib/libc.musl-x86_64.so.1
curl -fsSL https://claude.ai/install.sh | bash # installs musl build
claude # -> statx error

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.179

Claude Code Version

2.1.181 (if it could run)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗