Spurious glibc Version Error When Using Build Scripts #724

Alexhuszagh · 2022-05-27T16:31:02Z

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:

Use a custom target directory for each cross-compilation target (--target-dir path/to/x).
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.

The text was updated successfully, but these errors were encountered:

Emilgardis · 2022-05-27T18:21:14Z

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 · 2022-05-27T18:31:55Z

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

Alexhuszagh · 2022-06-03T18:10:16Z

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 · 2022-06-06T12:30:04Z

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

Alexhuszagh · 2022-06-06T14:20:15Z

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.

Required to patch cross-rs#724 without deleting the entire volume for persistent data volumes. A few changes were required: the entire `/cross` mount prefix must be owned by the user so `/cross/target` can be removed. Next, we use the full path to the mounted target directory, rather than the symlink, since `cargo clean` would just delete the symlink. Finally, we've added `cargo clean` to a list of known subcommands, and it only needs docker if we use a remote host.

CI is running into cross-rs/cross#724, which should be fixed if we clear the cache.

Emilgardis · 2023-01-09T05:57:20Z

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 · 2023-03-26T11:20:03Z

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 · 2023-06-03T22:39:04Z

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:

Create a new binary crate with chrono v0.4.26 as a dependency.
run cross build --release --target x86_64-unknown-linux-musl
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.

Prevent cross from considering the targets built for x86_64 fresh for aarch64. See: cross-rs/cross#724

denfren · 2023-07-17T17:44:04Z

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.

…cross-rs/cross#724

Building the whole project with `dotnet publish -c Release --os win` would fail with the message "glibc version 2.25 not found" this was related to caching problems while compiling the build script and a workaround is specifying a different target directory for each target that should be build. See also the following issues for more details about the problem: - cross-rs/cross#988 - cross-rs/cross#724

Unfortunately the follwing problem was reintroduced because the linux target was removed without checking if debug builds still worked. Issue: cross-rs/cross#724

Seeing if [this](cross-rs/cross#724 (comment)) is a quick fix so I can avoid any deeper debugging.

* Update nokogiri to version with support for apple silicon * Update gem dependencies to address spec failures running with Ruby 3 * Require ActiveRecordAdapter from spec that uses it * Add support for both x86_64 and arm64 linux architectures * Build both x86 and arm dynamic libraries for ruby * Use Ruby 2.6 as minimum tested version and 3.2 for all ruby-related tasks Rationale: 2.6.10 is what ships with macOS 14.0 even though support for it stopped in March of 2022 and 3.2 is the latest stable version. * Ensure the ruby libs are copied and available for testing * Bump solargraph and rubocop Disable new cops for existing violations * Update bundler to get rid of SPELL_CHECKERS warning * Do not suggest extensions * Simplify YARD docs for query method Add the host and bindings parameters so calls that contain them don't fail typecheck * Must use Ruby 2.4 in order to build the docs on main * Must use Ruby 2.4 in order to build the docs on main * Use .ruby-version instead of hard-coding the current ruby version in Github actions The rationale for this is from the way that docs diffing works. Both the base branch and the new branch need to be able to build using the version of Ruby supported by that branch. Without this change, when a PR is introduced that updates the target Ruby version, a followup PR will be required to update the github action for building the 'base' branch's version of the docs. With this change, github actions will choose the version of Ruby targeted by the branch it is trying to build * Clippy * Cargo fmt * Test * Try building aarch64 first Seeing if [this](cross-rs/cross#724 (comment)) is a quick fix so I can avoid any deeper debugging. * Keep shuffling the deck chairs * Revert "Test" This reverts commit 7feebd1. * Add 0.27.3 changelog * Bump version * Let's just release now instead --------- Co-authored-by: Gabe Jackson <[email protected]>

Alexhuszagh added bug container-images A-powerpc Area: PowerPC targets labels May 27, 2022

Alexhuszagh changed the title ~~glibc version error in powerpc64-unknown-linux-gnu target~~ glibc version error in nightly targets May 27, 2022

Alexhuszagh removed the A-powerpc Area: PowerPC targets label May 27, 2022

Alexhuszagh closed this as completed May 27, 2022

Alexhuszagh mentioned this issue Jun 3, 2022

centos7 /lib64/libc.so.6: version `GLIBC_2.18' not found #711

Closed

Emilgardis reopened this Jun 6, 2022

Emilgardis changed the title ~~glibc version error in nightly targets~~ spurious glibc version error in build script build Jun 6, 2022

This was referenced Jun 8, 2022

feat: Parse Cargo's --manifest-path option to determine mounted docker root #494

Closed

Error of target x86_64-unknown-linux-gnu #793

Closed

make x86_64-unknown-linux-gnu ubuntu again #764

Merged

This was referenced Jun 21, 2022

Add comprehensive support for remote docker. #785

Merged

ring 0.16.20 fails on glibc for armv7-unknown-linux-gnueabihf #832

Closed

Alexhuszagh added the A-glibc Area: glibc targets label Jun 22, 2022

Emilgardis pinned this issue Jun 22, 2022

Alexhuszagh added the help wanted label Jun 23, 2022

ravenclaw900 mentioned this issue Jun 25, 2022

Glibc errors with v0.2.2 #858

Closed

11 tasks

taiki-e mentioned this issue Jun 28, 2022

The scope of the unsafe block can be appropriately reduced tokio-rs/tokio#4700

Closed

Darksonn added a commit to tokio-rs/tokio that referenced this issue Jun 29, 2022

chore: disable caching for cross jobs

62df3c5

CI is running into cross-rs/cross#724, which should be fixed if we clear the cache.

Darksonn mentioned this issue Jun 29, 2022

chore: disable caching for cross jobs tokio-rs/tokio#4794

Merged

Darksonn added a commit to tokio-rs/tokio that referenced this issue Jun 29, 2022

chore: disable caching for cross jobs (#4794)

79d8024

CI is running into cross-rs/cross#724, which should be fixed if we clear the cache.

Alexhuszagh mentioned this issue Sep 8, 2022

cross fails to recompile build script correctly when there are project changes #1014

Closed

11 tasks

Emilgardis mentioned this issue Oct 4, 2022

can it work with cross? Swatinem/rust-cache#42

Open

Alexhuszagh mentioned this issue Oct 10, 2022

Support (or not) multi-target invocation #1062

Open

2 tasks

AaronKutch mentioned this issue Oct 31, 2022

Eth 2.0 Production onomyprotocol/arc#109

Closed

This was referenced Jan 9, 2023

cross fail to build futures-util v0.3.25 due to version GLIBC_2.28' not found` #1184

Open

cross should be built on ubuntu 18.04 (fails with version GLIBC_2.29' not found`) actions-rs/cargo#204

Open

Emilgardis mentioned this issue Feb 7, 2023

x86_64-pc-windows-gnu: version `GLIBC_2.28' not found #1205

Closed

11 tasks

This was referenced Mar 27, 2023

aarch64-unknown-linux-gnu: glibc out of date #1237

Closed

Immediately Terminates with "'rustc --print target-list' failed" #526

Closed

Emilgardis mentioned this issue May 4, 2023

Failed to run build command for libc, failed to get rustc version #1189

Open

11 tasks

lu-zero added a commit to sifis-home/third-party-application that referenced this issue Jun 14, 2023

fix: Make sure cross works on a clean run

acca4ae

Prevent cross from considering the targets built for x86_64 fresh for aarch64. See: cross-rs/cross#724

newtykip added a commit to newtykip/johnny that referenced this issue Jul 17, 2023

fix: okay apparently it's not my fault cross-rs/cross#724

2bd8101

FlareFlo added a commit to Warthunder-Open-Source-Foundation/wt_ext_cli that referenced this issue Oct 9, 2023

HACK: Clean cross build cache before building to avoid suspected issue …

dc0dd17

…cross-rs/cross#724

Emilgardis mentioned this issue Oct 12, 2023

Issue when building with cross rustdoc #1341

Closed

11 tasks

Emilgardis mentioned this issue Oct 23, 2023

Problem with aarch64-unknown-linux-gnu #1354

Closed

0xfourzerofour mentioned this issue Oct 24, 2023

ci: release pipeline with cross-arch builds alchemyplatform/rundler#421

Closed

gj added a commit to jdeff/oso that referenced this issue Jan 12, 2024

Try building aarch64 first

9e08687

Seeing if [this](cross-rs/cross#724 (comment)) is a quick fix so I can avoid any deeper debugging.

This was referenced Jan 22, 2024

Native libs compiled against 2.29 instead of 2.24 glibc. pact-foundation/pact-reference#354

Closed

chore: migrate target/artifacts to release_artifacts to avoid cargo clean loss pact-foundation/pact-reference#374

Merged

Emilgardis mentioned this issue Feb 5, 2024

GLIBC_2.29 not found in ghcr.io/cross-rs/aarch64-unknown-linux-musl:0.2.5 #1436

Closed

11 tasks

joepio mentioned this issue Feb 6, 2024

Musl build CI failure - failed to run custom build command for libc v0.2.152 atomicdata-dev/atomic-server#833

Closed

MoAlyousef mentioned this issue Mar 23, 2024

WHat backend to use on a Raspberry Pi (Zero 2) MoAlyousef/soloud-rs#36

Closed

YOU54F mentioned this issue May 9, 2024

chore: build linux x86_64 ffi against glibc 2.23 pact-foundation/pact-reference#413

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Spurious glibc Version Error When Using Build Scripts #724

Spurious glibc Version Error When Using Build Scripts #724

Alexhuszagh commented May 27, 2022 •

edited

Emilgardis commented May 27, 2022

Alexhuszagh commented May 27, 2022

Alexhuszagh commented Jun 3, 2022

Emilgardis commented Jun 6, 2022

Alexhuszagh commented Jun 6, 2022

Emilgardis commented Jan 9, 2023

Imyr commented Mar 26, 2023 •

edited

WillBuik commented Jun 3, 2023

denfren commented Jul 17, 2023 •

edited

Spurious glibc Version Error When Using Build Scripts #724

Spurious glibc Version Error When Using Build Scripts #724

Comments

Alexhuszagh commented May 27, 2022 • edited

Issue Description

Update

Version Info

Emilgardis commented May 27, 2022

Alexhuszagh commented May 27, 2022

Alexhuszagh commented Jun 3, 2022

Emilgardis commented Jun 6, 2022

Alexhuszagh commented Jun 6, 2022

Emilgardis commented Jan 9, 2023

Imyr commented Mar 26, 2023 • edited

WillBuik commented Jun 3, 2023

denfren commented Jul 17, 2023 • edited

Alexhuszagh commented May 27, 2022 •

edited

Imyr commented Mar 26, 2023 •

edited

denfren commented Jul 17, 2023 •

edited