Skip to content

fix(release): build x86_64-unknown-linux-gnu natively instead of with cross#324

Merged
rubberduck203 merged 1 commit into
mainfrom
fix/release-x86-use-native-build
Jun 1, 2026
Merged

fix(release): build x86_64-unknown-linux-gnu natively instead of with cross#324
rubberduck203 merged 1 commit into
mainfrom
fix/release-x86-use-native-build

Conversation

@rubberduck203
Copy link
Copy Markdown
Contributor

Summary

  • The Release workflow has been failing on the x86_64-unknown-linux-gnu target since the opentelemetry 0.32 stack was bumped (that bump brought rustls 0.23 → aws-lc-rsaws-lc-sys into the dep tree).
  • aws-lc-sys's build script panics when it detects a GCC memcmp bug (gcc.gnu.org/bugzilla/95189, fixed in GCC 10.4). The ghcr.io/cross-rs/x86_64-unknown-linux-gnu:main Docker image ships GCC < 10.4, so the check always trips.
  • The other three targets (aarch64-apple-darwin, aarch64-unknown-linux-gnu, x86_64-unknown-linux-musl) all passed because they use different images or don't hit this code path.
  • x86_64-unknown-linux-gnu is the native target on the ubuntu-latest runner — we don't need cross at all for it. Switching to use-cross: false builds it with plain cargo, which uses the host GCC (Ubuntu 24.04 ships GCC 13) and sidesteps the issue entirely.

Test plan

  • Confirm the Release workflow passes all four build targets after merge
  • Verify the x86_64-unknown-linux-gnu artifact is produced correctly

🤖 Generated with Claude Code

… cross

The cross Docker image for x86_64-unknown-linux-gnu uses GCC < 10.4, which
triggers an aws-lc-sys build-time panic (GCC memcmp bug, gcc.gnu.org/bugzilla/95189).
x86_64-unknown-linux-gnu is the native target on the ubuntu-latest runner, so
cross-compilation is unnecessary here.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@rubberduck203 rubberduck203 merged commit e3d08d8 into main Jun 1, 2026
8 checks passed
@rubberduck203 rubberduck203 deleted the fix/release-x86-use-native-build branch June 1, 2026 15:32
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