›_ Codex Issues
Codex Issues / #10587

Codex RS build failing with Errors on Aarch64 Rocky Linux 8

Resolved 💬 2 comments Opened Feb 4, 2026 by datalogics-robb Closed Feb 5, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What issue are you seeing?

I set up a Jenkins job to build Codex from source on x86_64 and Aarch64 Rocky Linux 8. This was working through version 0.89.0 and since has been failing due to compiler errors.

What steps can reproduce the bug?

Follow build from source instructions for Linux, on Rocky Linux 8 on AArch64.

What is the expected behavior?

Builds complete on ARMv8 Linux

Additional information

build log for Codex-rs:

log.txt

View original on GitHub ↗

2 Comments

etraut-openai contributor · 6 months ago

You'll probably need to do some diagnosis yourself, as this isn't a platform we target.

Here's an analysis supplied by Codex:

We were able to narrow this down to a native toolchain issue introduced after 0.89.0. Starting in 0.90.0, Codex began pulling in rama-tls-boring / rama-boring-sys (for the network proxy stack), which builds BoringSSL during cargo build.

Your failure is in that BoringSSL C/C++ build step (not Rust compilation), with:

  • gcc/g++ 8.5.0 on Rocky 8 (aarch64)
  • -Werror=attributes triggered by alignment warnings in [p256-nistz.cc.inc](app://-/index.html#)

That matches what we’d expect from older GCC toolchains on this dependency path.

Workarounds:

  • Build with a newer compiler toolchain (recommended), e.g. clang or newer GCC (GCC 11+).
  • Use a newer distro/toolchain environment (our CI builds on Ubuntu 24.04 with newer compilers).
datalogics-robb · 6 months ago

Modifying the environment to use clang++ 18.1 resolved this issue with build errors