cross-rs/cross

Spurious glibc Version Error When Using Build Scripts

Alexhuszagh opened this issue · 11 comments

Alexhuszagh commented

Issue Description

When using build scripts, even if rustc changes (path or target), cargo won't always do a full re-compile, and this can lead to spurious glibc errors. This is linked to rust-lang/cargo#10367 (comment). Since we change targets all the time, we're much more likely to cause this "feature" to manifest than standard builds.

There's 2 solutions:

  1. Use a custom target directory for each cross-compilation target (--target-dir path/to/x).
  2. Use cargo clean when the error appears.

More detailed information and a robust workaround are found on the wiki.

Update

This seems to happen sporadically, with any mixing of toolchains or targets. The issue occurs sporadically when the toolchain changes, and seems to be related to #858 (comment). The solution seems to be running cargo clean (with the appropriate target dir), but there needs to be a better solution.

Version Info

$ cross --version
cross 0.2.1 (459e03e 2022-05-26)
Warning: Falling back to `cargo` on the host.
cargo 1.63.0-nightly (39ad1039d 2022-05-25)

Sample code to reproduce:

$ git clone https://github.com/cross-rs/rust-cpp-hello-word
$ cd rust-cpp-hello-word
$ cross run --target powerpc64-unknown-linux-gnu --verbose
+ "rustc" "--print" "sysroot"
+ "rustup" "toolchain" "list"
+ "rustup" "target" "list" "--toolchain" "nightly-x86_64-unknown-linux-gnu"
+ "rustup" "component" "list" "--toolchain" "nightly-x86_64-unknown-linux-gnu"
+ "/usr/bin/docker" "run" "--userns" "host" "-e" "PKG_CONFIG_ALLOW_CROSS=1" "--rm" "--user" "1000:1000" "-e" "XARGO_HOME=/xargo" "-e" "CARGO_HOME=/cargo" "-e" "CARGO_TARGET_DIR=/target" "-e" "USER=ahuszagh" "-e" "CROSS_RUNNER=" "-v" "/home/ahuszagh/.xargo:/xargo:Z" "-v" "/home/ahuszagh/.cargo:/cargo:Z" "-v" "/cargo/bin" "-v" "/home/ahuszagh/Desktop/cross/rust-cpp-hello-word:/project:Z" "-v" "/home/ahuszagh/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu:/rust:Z,ro" "-v" "/home/ahuszagh/Desktop/cross/rust-cpp-hello-word/target:/target:Z" "-w" "/project" "-i" "-t" "ghcr.io/cross-rs/powerpc64-unknown-linux-gnu:main" "sh" "-c" "PATH=$PATH:/rust/bin cargo run --target powerpc64-unknown-linux-gnu --verbose"
       Fresh cc v1.0.73
   Compiling hellopp v0.1.0 (/project)
     Running `/target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build`
error: failed to run custom build command for `hellopp v0.1.0 (/project)`

Caused by:
  process didn't exit successfully: `/target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build` (exit status: 1)
  --- stderr
  /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build)
  /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build)

This should compile normally, however, we are unable to find the appropriate glibc version. This was detected while debugging #441.

Emilgardis commented

I can't replicate this with nightly 2022-05-26 on windows with the latest powerpc64 image (sha256:d52b1c1e2f0666cf8e244e890f8e6dfe1907e427e394de10d11c385ae728912c)

❯ cross run --target powerpc64-unknown-linux-gnu --verbose
+ "cargo" "metadata" "--format-version=1" "--filter-platform" "powerpc64-unknown-linux-gnu" "--features" ""
+ "rustc" "--print" "sysroot"
+ "rustup" "toolchain" "list"
Warning: using newer rustc `1.63.0-nightly (490324f7b 2022-05-26)` for the target. Current active rustc on the host is `rustc 1.63.0-nightly (76761db59 2022-05-24)`.
 > Update with `rustup update`
+ "rustup" "target" "list" "--toolchain" "nightly-x86_64-unknown-linux-gnu"
+ "rustup" "component" "list" "--toolchain" "nightly-x86_64-unknown-linux-gnu"
+ "C:\\WINDOWS\\system32\\wsl.exe" "-e" "wslpath" "-a" "G:\\workspace\\small dev space\\cross-issue724\\rust-cpp-hello-word"
+ "C:\\WINDOWS\\system32\\wsl.exe" "-e" "wslpath" "-a" "G:\\workspace\\small dev space\\cross-issue724\\rust-cpp-hello-word"
+ "C:\\Program Files\\Docker\\Docker\\resources\\bin\\docker.EXE" "run" "--userns" "host" "-e" "PKG_CONFIG_ALLOW_CROSS=1" "--rm" "-e" "XARGO_HOME=/xargo" "-e" "CARGO_HOME=/cargo" "-e" "CARGO_TARGET_DIR=/target" "-e" "USER=Emil" "-e" "CROSS_RUNNER=" "-v" "C:\\Users\\Emil\\.xargo:/xargo:Z" "-v" "C:\\Users\\Emil\\.cargo:/cargo:Z" "-v" "/cargo/bin" "-v" "G:\\workspace\\small dev space\\cross-issue724\\rust-cpp-hello-word:/project:Z" "-v" "C:\\Users\\Emil\\.rustup\\toolchains\\nightly-x86_64-unknown-linux-gnu:/rust:Z,ro" "-v" "G:\\workspace\\small dev space\\cross-issue724\\rust-cpp-hello-word\\target:/target:Z" "-w" "/project" "-i" "-t" "ghcr.io/cross-rs/powerpc64-unknown-linux-gnu:main" "sh" "-c" "PATH=$PATH:/rust/bin cargo run --target powerpc64-unknown-linux-gnu --verbose"
   Compiling cc v1.0.73
     Running `rustc --crate-name cc --edition=2018 /cargo/registry/src/github.com-1ecc6299db9ec823/cc-1.0.73/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C metadata=8451de8edbca495a -C extra-filename=-8451de8edbca495a --out-dir /target/debug/deps -L dependency=/target/debug/deps --cap-lints allow`
   Compiling hellopp v0.1.0 (/project)
     Running `rustc --crate-name build_script_build build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=0a565c6e09d5b0ce -C extra-filename=-0a565c6e09d5b0ce --out-dir /target/debug/build/hellopp-0a565c6e09d5b0ce -C incremental=/target/debug/incremental -L dependency=/target/debug/deps --extern cc=/target/debug/deps/libcc-8451de8edbca495a.rlib`
     Running `/target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build`
     Running `rustc --crate-name hellopp src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=fc5c3be60a3d8fee -C extra-filename=-fc5c3be60a3d8fee --out-dir /target/powerpc64-unknown-linux-gnu/debug/deps --target powerpc64-unknown-linux-gnu -C linker=powerpc64-linux-gnu-gcc -C incremental=/target/powerpc64-unknown-linux-gnu/debug/incremental -L dependency=/target/powerpc64-unknown-linux-gnu/debug/deps -L dependency=/target/debug/deps -L native=/target/powerpc64-unknown-linux-gnu/debug/build/hellopp-618833d9398f1fb8/out -l static=hellopp -l stdc++`
    Finished dev [unoptimized + debuginfo] target(s) in 30.29s
     Running `/linux-runner powerpc64 /target/powerpc64-unknown-linux-gnu/debug/hellopp`
Hello, world!
Alexhuszagh commented

Running cargo clean fixed this, so it might be a build fingerprint issue or incremental build issue. Either way, not replicating for me anymore.

  • 👍1
Alexhuszagh commented

I'm getting this when I mix the nightly and stable toolchains for a given target.

$ cross run --target armv7-unknown-linux-gnueabihf
    Finished dev [unoptimized + debuginfo] target(s) in 0.11s
     Running `/linux-runner armv7 /target/armv7-unknown-linux-gnueabihf/debug/hellopp`
Hello, world!
$ cross run +nightly --target armv7-unknown-linux-gnueabihf
Warning: using newer rustc `1.63.0-nightly (490324f7b 2022-05-26)` for the target. Current active rustc on the host is `rustc 1.61.0 (fe5b13d68 2022-05-18)`.
 > Update with `rustup update`
   Compiling hellopp v0.1.0 (/project)
error: failed to run custom build command for `hellopp v0.1.0 (/project)`

Caused by:
  process didn't exit successfully: `/target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build` (exit status: 1)
  --- stderr
  /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build)
  /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build)
  /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build)
  /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by /target/debug/build/hellopp-0a565c6e09d5b0ce/build-script-build)

We might have to document this as a known issue. Thoughts @Emilgardis?

Emilgardis commented

I want to know why this happens. Is the build script not invalidated with different toolchains?

Alexhuszagh commented

Still not sure, it doesn't reproduce very frequently. I think it's the above, but it should be invalidated and most of the time it is.

Alexhuszagh commented

I'm getting issue just building cross with cargo for when switching between Windows-native and WSL with an identical error message, suggesting to me this isn't cross-specific:

$ cargo build --workspace
  Downloaded yaml-rust v0.4.5
  Downloaded pin-project-lite v0.2.9
  Downloaded thread_local v1.1.4
  Downloaded tracing v0.1.35
...
error: failed to run custom build command for `cross v0.2.2 (/mnt/c/Users/ahusz/git/cross)`

Caused by:
  process didn't exit successfully: `/mnt/c/Users/ahusz/git/cross/target/debug/build/cross-ea1bcf56ddb8e6e9/build-script-build` (exit status: 1)
  --- stderr
  /mnt/c/Users/ahusz/git/cross/target/debug/build/cross-ea1bcf56ddb8e6e9/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /mnt/c/Users/ahusz/git/cross/target/debug/build/cross-ea1bcf56ddb8e6e9/build-script-build)
  /mnt/c/Users/ahusz/git/cross/target/debug/build/cross-ea1bcf56ddb8e6e9/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /mnt/c/Users/ahusz/git/cross/target/debug/build/cross-ea1bcf56ddb8e6e9/build-script-build)
  /mnt/c/Users/ahusz/git/cross/target/debug/build/cross-ea1bcf56ddb8e6e9/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /mnt/c/Users/ahusz/git/cross/target/debug/build/cross-ea1bcf56ddb8e6e9/build-script-build)
warning: build failed, waiting for other jobs to finish...

This might be an issue in cc-rs.

Emilgardis commented

It boils down to reusing build-scripts between different systems with different versions available. I think it could be labeled a cargo issue. #858 (comment)

Emilgardis commented

Been trying to make a consistent reproduction of this but nothing seems to work to reproduce it. I think what we need to do is identify exactly when this happens, and then if there are any other workarounds aside from cargo clean, I still suspect -Zbinary-dep-depinfo would solve this.

I've been trying to reproduce it with cargo build and then cross build, but nothing reproduces it in the build script (I have been able to reproduce it without a build-script, but that's another case). See https://github.com/Emilgardis/cross-issue724/actions/workflows/ci.yml

Imyr commented

In my particular case, it happens when cross build --release is used.
just cross build gives no such error.
Thought it would help.

Status: Downloaded newer image for ghcr.io/cross-rs/aarch64-unknown-linux-gnu:main
   Compiling libc v0.2.139
error: failed to run custom build command for `libc v0.2.139`

Caused by:
  process didn't exit successfully: `/target/release/build/libc-4e3b2cf9f91fdbab/build-script-build` (exit status: 1)
  --- stderr
  /target/release/build/libc-4e3b2cf9f91fdbab/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /target/release/build/libc-4e3b2cf9f91fdbab/build-script-build)
  /target/release/build/libc-4e3b2cf9f91fdbab/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /target/release/build/libc-4e3b2cf9f91fdbab/build-script-build)
  /target/release/build/libc-4e3b2cf9f91fdbab/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /target/release/build/libc-4e3b2cf9f91fdbab/build-script-build)
warning: build failed, waiting for other jobs to finish...
Error: Process completed with exit code 101.

Running cross on Github Actions, snippet attached;

         cargo build --release &&
         mv target/release/bitnet target/release/bitnet-linux-gnu-x86_64 &&
         cargo install cross --git https://github.com/cross-rs/cross &&
         sudo apt-get install qemu binfmt-support qemu-user-static &&
         docker run --privileged --rm tonistiigi/binfmt --install all &&
         rustup target install aarch64-unknown-linux-gnu &&
         cross build --target aarch64-unknown-linux-gnu &&
         mv target/aarch64-unknown-linux-gnu/debug/bitnet target/release/bitnet-linux-gnu-aarch64 &&
         rustup target install aarch64-linux-android &&
         cross build --target aarch64-linux-android &&
         mv target/aarch64-linux-android/debug/bitnet target/release/bitnet-linux-android-aarch64

Dependencies in Cargo.toml file;

[dependencies]
reqwest = "0.11.13"
html-escape = "0.2.13"
tokio = { version = "1", features = ["macros"] }
clap = { version = "4.1.4", features = ["derive"] }
openssl = { version = "0.10.45", features = ["vendored"] }
git2 = {version = "0.13.22", features = ["vendored-libgit2"]}

EDIT:

        mkdir release &&
        cargo build --release &&
        mv target/release/bitnet release/bitnet-linux-gnu-x86_64 &&
        cargo install cross --git https://github.com/cross-rs/cross &&
        sudo apt-get install qemu binfmt-support qemu-user-static &&
        docker run --privileged --rm tonistiigi/binfmt --install all &&
        cargo clean &&
        rustup target install aarch64-unknown-linux-gnu &&
        cross build --release --target aarch64-unknown-linux-gnu &&
        mv target/aarch64-unknown-linux-gnu/release/bitnet release/bitnet-linux-gnu-aarch64 &&
        cargo clean &&
        rustup target install aarch64-linux-android &&
        cross build --release --target aarch64-linux-android &&
        mv target/aarch64-linux-android/release/bitnet release/bitnet-linux-android-aarch64

using cargo clean as suggested worked.

WillBuik commented

I'm not certain it is the same issue but I have a consistent and simple way to repro something like this
with cross build --release. Running cargo clean doesn't work around it, you need to use
separate target directories.

Steps:

  1. Create a new binary crate with chrono v0.4.26 as a dependency.
  2. run cross build --release --target x86_64-unknown-linux-musl
  3. run cross build --release --target aarch64-unknown-linux-musl

The second cross build will fail with:

error: failed to run custom build command for `num-traits v0.2.15`

Caused by:
  process didn't exit successfully: `/target/release/build/num-traits-60547cd1ad1882f5/build-script-build` (exit status: 1)
  --- stderr
  /target/release/build/num-traits-60547cd1ad1882f5/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /target/release/build/num-traits-60547cd1ad1882f5/build-script-build)
  /target/release/build/num-traits-60547cd1ad1882f5/build-script-build: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /target/release/build/num-traits-60547cd1ad1882f5/build-script-build)

I am running this on an Intel Mac with Docker Desktop with rustc 1.72.0-nightly (871b59520 2023-05-31) on the host.

  • 👍3
denfren commented

I noticed that the order seems to matter. Building aarch64 first consistently works for me while building x86_64 first consistently fails. This is when compiling after cargo clean...results get random once anything was compiled.