Skip to content

Use cross for Linux builds to ensure glibc 2.31 compatibility#67

Merged
thisnick merged 1 commit intomainfrom
claude/glibc-version-compatibility-kF56O
Feb 26, 2026
Merged

Use cross for Linux builds to ensure glibc 2.31 compatibility#67
thisnick merged 1 commit intomainfrom
claude/glibc-version-compatibility-kF56O

Conversation

@thisnick
Copy link
Copy Markdown
Owner

Summary

Updated the release build workflow to use the cross tool for Linux targets, ensuring binaries are compatible with glibc 2.31 and older systems. This prevents the ubuntu-latest (24.04) environment from producing binaries that require glibc 2.39+.

Changes

  • Added a new step to install the cross tool for Linux builds
  • Created a separate build step for Linux targets using cross build instead of cargo build
  • Updated the existing build step to skip Linux targets (only runs for non-Linux platforms)
  • Added explanatory comments documenting the rationale for using cross

Implementation Details

The workflow now conditionally uses cross for any target containing "linux" in its name, while maintaining the existing cargo build approach for other platforms (macOS, Windows, etc.). This ensures broad compatibility across different glibc versions without affecting the build process for non-Linux targets.

https://claude.ai/code/session_01PgK6kkizuvPvv6oq1Ku2QW

…ibility

The release workflow was building on ubuntu-latest (Ubuntu 24.04), which
produced binaries requiring glibc 2.39+. This made the binaries incompatible
with most Linux distributions (only Ubuntu 24.04+ and Fedora 40+ worked).

Switch Linux builds to use the `cross` tool, which compiles inside Docker
containers with an older glibc (2.31). This makes the binaries compatible
with Ubuntu 20.04+, Debian 11+, RHEL 9+, Fedora 33+, and most other
modern Linux distributions.

https://claude.ai/code/session_01PgK6kkizuvPvv6oq1Ku2QW
@thisnick thisnick merged commit 71afadc into main Feb 26, 2026
5 checks passed
@thisnick thisnick deleted the claude/glibc-version-compatibility-kF56O branch February 26, 2026 04:55
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.

2 participants