Build fully static amd64 + arm64 Linux binaries for Rust projects with vendored OpenSSL and ring -- no flaky toolchain servers needed.
Cross-compiling Rust to aarch64-unknown-linux-musl on x86_64 GitHub Actions runners is painful:
| Approach | Problem |
|---|
Abdulrhman Alkhodiry aalkhodiry
aalkhodiry
/ cargo-zigbuild-musl-cross-compile.md
Created
February 16, 2026 17:03
Cross-Compiling Rust to Static musl Binaries with cargo-zigbuild on GitHub Actions (amd64 + arm64)
aalkhodiry
/ rust-aarch64-musl-cross-compile.md
Created
February 16, 2026 16:28
Cross-Compiling Rust for aarch64-unknown-linux-musl on GitHub Actions (with vendored OpenSSL + ring)
With vendored OpenSSL + ring (rustls) -- a complete working guide.
Cross-compiling Rust projects targeting aarch64-unknown-linux-musl on x86_64 GitHub Actions runners fails when:
- Using
gcc-aarch64-linux-gnu(glibc cross-compiler) with musl target -- vendored OpenSSL gets compiled against glibc headers, introducing symbols like__memcpy_chk,__memset_chk,__vfprintf_chkthat don't exist in musl.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/bin/bash | |
| # Function to display usage information | |
| usage() { | |
| echo "Usage: $0 /path/to/input.mp4 [ /path/to/output_directory ]" | |
| exit 1 | |
| } | |
| # Check if at least one argument (input file) is provided | |
| if [ $# -lt 1 ]; then |