Skip to content

fix(build): use the musl suffix for source-built binaries - #2471

Open
xunguangzlj-cloud wants to merge 2 commits into
vercel-labs:mainfrom
xunguangzlj-cloud:fix/source-build-musl-name
Open

xunguangzlj-cloud wants to merge 2 commits into
vercel-labs:mainfrom
xunguangzlj-cloud:fix/source-build-musl-name

Conversation

@xunguangzlj-cloud

Copy link
Copy Markdown

Problem

On a musl Linux host, the source build copies the executable to bin/agent-browser-linux-x64. The JavaScript launcher looks for bin/agent-browser-linux-musl-x64, so it cannot start the executable the build just produced.

Change

Use the launcher's existing libc detection in the copy script so both choose the same filename. The glibc and non-Linux names stay the same.

Verification

  • The new musl regression fails on main with “No binary found” and passes after the fix.
  • The glibc control and four existing launcher cases also pass. The six cases ran on Ubuntu with Node 24.16.0.
  • The Linux cases supply musl and glibc ldd output, then run the actual copy script and launcher against a fixture executable. A Rust build on Alpine was outside this check.
  • Version sync, JavaScript syntax, and diff checks passed.

Authored with OpenAI Codex (GPT-6).

@vercel

vercel Bot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

@xunguangzlj-cloud is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant