-
Notifications
You must be signed in to change notification settings - Fork 13.4k
ui/feature-gates/version_check.rs broken with rpath=false #141579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
That test invokes raw
|
That should be converted to a run-make test and fixed like #140843 let mut rustc = bare_rustc(); // <- handles host rpath libs
// do the version check logic
// ... |
sounds like the right approach - should I prepare an MR or will you? :) |
I won't get to this super soon, PRs welcomed :) |
github-actions bot
pushed a commit
to rust-lang/miri
that referenced
this issue
May 28, 2025
…path-false, r=jieyouxu test: convert version_check ui test to run-make else it breaks with `rpath=false`. Fixes: rust-lang/rust#141579
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Summary
this test case is only executed on
x86
(notx86_64
or other targets, which already seems wrong, but might be the reason this was not caught/reported yet?).it tries to execute the stage2
rustc
binary without settingLD_LIBRARY_LOAD_PATH
correctly, at least forrpath=false
:Command used
RUST_BACKTRACE=1 python3 src/bootstrap/bootstrap.py -j XXX --stage 2 --config debian/config.toml --on-fail env test --no-fail-fast --exclude src/tools/tidy
Expected behaviour
the test should pass :)
Actual behaviour
adding some debug code shows that
version
isOk("")
(i.e., stdout is empty), and the executed rustc binary is/build/reproducible-path/rustc-1.86.0+dfsg1/build/i686-unknown-linux-gnu/stage2/bin/rustc"
. dumping the test commandsstderr
instead ofstdout
, we get the actual error:/build/reproducible-path/rustc-1.86.0+dfsg1/build/i686-unknown-linux-gnu/stage2/bin/rustc: error while loading shared libraries: librustc_driver-b27aa4671471dea1.so: cannot open shared object file: No such file or directory\n"
Bootstrap configuration (bootstrap.toml)
this happened during the Debian package build.
the config is heavily modified to suite distro purposes, but we don't carry any bootstrap or compiletest patches that should cause this:
minimizing this config when testing from git 1.86 or master to just:
with the following diff to run on 64-bit x86:
and the following command:
reproduces the issue as well. without
rpath=false
it works.Operating system
Debian experimental
HEAD
1.86 tarball
Additional context
Build Log
The text was updated successfully, but these errors were encountered: