{"version":"2.1.225","anchor":"sdk-spawn-failures-explain-musl-glibc-loader-mismatches","canonical_anchor":"sdk-spawn-failures-explain-musl-glibc-loader-mismatches","heading":"SDK spawn failures explain musl\/glibc loader mismatches","tier":"use","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/sdk-spawn-failures-explain-musl-glibc-loader-mismatches","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### SDK spawn failures explain musl\/glibc loader mismatches\n\nSDK spawn errors now explain musl\/glibc binary mismatches and tell you which option overrides the path.\n\n**What**\n\nWhen the configured Claude Code executable exists but cannot be spawned, the SDK error now describes the dynamic-loader mismatch case and points at the option you would use to fix it.\n\n**Details**\n\n- covers the case of a musl-linked binary on a glibc host, where `\/lib\/ld-musl-*` is absent\n- names `options.pathToClaudeCodeExecutable` as the override\n\n**Evidence**\n\n`e.g. spawning a musl-linked binary on a glibc Linux host fails because the musl dynamic loader (\/lib\/ld-musl-*) is missing`\n\n- Area: SDK\n- Names: `options.pathToClaudeCodeExecutable`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 0\/5"}