process didn't exit successfully: codex-0.117.0

What version of Codex CLI is running?

0.117.0

What subscription do you have?

Downstream package build process for end-users

Which model were you using?

_No response_

What platform is your computer?

Linux

What terminal emulator and version are you using (if applicable)?

_No response_

What issue are you seeing?

We build codex cli in Network-less environment for security and reproducible builds, with dependencies vendored with cargo vendor. Version 0.117.0 started to fail with:

     Running `/usr/src/RPM/BUILD/codex-0.117.0/codex-rs/target/release/build/v8-c84d72cc9b02f64a/build-script-build`
error: failed to run custom build command for `v8 v146.4.0`
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_RELEASE_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information ge
neration.

Caused by:
  process didn't exit successfully: `/usr/src/RPM/BUILD/codex-0.117.0/codex-rs/target/release/build/v8-c84d72cc9b02f64a/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=.gn
  cargo:rerun-if-changed=BUILD.gn
  cargo:rerun-if-changed=src/binding.cc
  cargo:rerun-if-env-changed=CCACHE
  cargo:rerun-if-env-changed=CLANG_BASE_PATH
  cargo:rerun-if-env-changed=CXXSTDLIB
  cargo:rerun-if-env-changed=DENO_TRYBUILD
  cargo:rerun-if-env-changed=DOCS_RS
  cargo:rerun-if-env-changed=GN
  cargo:rerun-if-env-changed=GN_ARGS
  cargo:rerun-if-env-changed=HOST
  cargo:rerun-if-env-changed=NINJA
  cargo:rerun-if-env-changed=OUT_DIR
  cargo:rerun-if-env-changed=RUSTY_V8_ARCHIVE
  cargo:rerun-if-env-changed=RUSTY_V8_MIRROR
  cargo:rerun-if-env-changed=RUSTY_V8_SRC_BINDING_PATH
  cargo:rerun-if-env-changed=SCCACHE
  cargo:rerun-if-env-changed=V8_FORCE_DEBUG
  cargo:rerun-if-env-changed=V8_FROM_SOURCE
  cargo:rerun-if-env-changed=PYTHON
  cargo:rerun-if-env-changed=DISABLE_CLANG
  cargo:rerun-if-env-changed=EXTRA_GN_ARGS
  cargo:rerun-if-env-changed=PRINT_GN_ARGS
  cargo:rerun-if-env-changed=CARGO_ENCODED_RUSTFLAGS
  cargo:rustc-link-lib=static=rusty_v8
  lockfile: "/usr/src/RPM/BUILD/codex-0.117.0/codex-rs/target/release/build/v8.fslock"
  cargo:rustc-env=RUSTY_V8_SRC_BINDING_PATH=/usr/src/RPM/BUILD/codex-0.117.0/vendor/v8/gen/src_binding_release_x86_64-unknown-linux-gnu.rs
  static lib URL: https://github.com/denoland/rusty_v8/releases/download/v146.4.0/librusty_v8_release_x86_64-unknown-linux-gnu.a.gz
  cargo:rustc-link-search=/usr/src/RPM/BUILD/codex-0.117.0/codex-rs/target/release/gn_out/obj
  Looking for download in '"/usr/src/.cargo/.rusty_v8/https___github_com_denoland_rusty_v8_releases_download_v146_4_0_librusty_v8_release_x86_64_unknown_linux_gnu_a_gz"'
  Downloading https://github.com/denoland/rusty_v8/releases/download/v146.4.0/librusty_v8_release_x86_64-unknown-linux-gnu.a.gz
  Trying with Python...
  Python downloader failed, trying with curl.

  --- stderr

  thread 'main' (206593) panicked at /usr/src/RPM/BUILD/codex-0.117.0/vendor/v8/build.rs:692:14:
  called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }
  stack backtrace:
     0:     0x558a274534b2 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h28c9994a11a77647
     1:     0x558a27463a9a - core::fmt::write::h52772b2a2ed9212e
     2:     0x558a27429676 - std::io::Write::write_fmt::h6dc6b0a69b3ac944
     3:     0x558a274372b6 - std::panicking::default_hook::{{closure}}::h84582b71044b3c0f
     4:     0x558a27437116 - std::panicking::default_hook::h6d04774dc9933956
     5:     0x558a274374fb - std::panicking::panic_with_hook::h389d6119670120fb
     6:     0x558a27437378 - std::panicking::panic_handler::{{closure}}::h41fd715ca64e341f
     7:     0x558a274344a9 - std::sys::backtrace::__rust_end_short_backtrace::h15beba5a0134bb66
     8:     0x558a2741d04d - __rustc[43118a2d2b012dd]::rust_begin_unwind
     9:     0x558a270146ec - core::panicking::panic_fmt::h6ca03f28cb2c0209
    10:     0x558a270143e2 - core::result::unwrap_failed::h190d667b6bd3085d
    11:     0x558a27015d6e - core::result::Result<T,E>::unwrap::h3daff0ffcf52587d
                                 at /usr/src/RPM/BUILD/rust-1.94.1/library/core/src/result.rs:1233:23
    12:     0x558a27015d6e - build_script_build::download_file::hfe40f372e15060c8
                                 at /usr/src/RPM/BUILD/codex-0.117.0/vendor/v8/build.rs:692:14
    13:     0x558a270191fb - build_script_build::download_static_lib_binaries::h0d96496216adfacb
                                 at /usr/src/RPM/BUILD/codex-0.117.0/vendor/v8/build.rs:720:3
    14:     0x558a270191fb - build_script_build::main::h8e197a7043c6d922
                                 at /usr/src/RPM/BUILD/codex-0.117.0/vendor/v8/build.rs:123:3
    15:     0x558a2702b673 - core::ops::function::FnOnce::call_once::hd9254f0b8d10d1e0
                                 at /usr/src/RPM/BUILD/rust-1.94.1/library/core/src/ops/function.rs:250:5
    16:     0x558a2702b673 - std::sys::backtrace::__rust_begin_short_backtrace::hf9b7f934b7a9a337
                                 at /usr/src/RPM/BUILD/rust-1.94.1/library/std/src/sys/backtrace.rs:166:18
    17:     0x558a2702ad59 - std::rt::lang_start::{{closure}}::h18b86e6ac585c27e
                                 at /usr/src/RPM/BUILD/rust-1.94.1/library/std/src/rt.rs:206:18
    18:     0x558a2742ae26 - std::rt::lang_start_internal::hb8250d75e82623b3
    19:     0x558a27024bdc - main
    20:     0x7f084e2c51ae - <unknown>
    21:     0x7f084e2c5269 - __libc_start_main
    22:     0x558a27014715 - _start
    23:                0x0 - <unknown>
warning: build failed, waiting for other jobs to finish...

0.116.0 was built ok.

What steps can reproduce the bug?

cargo build in Network-less env using cargo vedor'ed sources.

What is the expected behavior?

_No response_

Additional information

_No response_