-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
ld.so: $LIB dynamic linking tokens expand to lib instead of lib32 on 32bit #101597
Comments
I marked this as stale due to inactivity. → More info |
Still important to me. |
But for our EDIT: I mean, I can imagine it all changed, but I'd expect that to have quite non-trivial consequences and thus need substantial motivation. |
Yeah, I don't think it would be a good idea to change this globally, especially if we only do this for Luckily, for vkBasalt & MangoHud, |
There is some "multi-lib stdenv" but I don't know the status: {
# A stdenv capable of building 32-bit binaries. On x86_64-linux,
# it uses GCC compiled with multilib support; on i686-linux, it's
# just the plain stdenv.
stdenv_32bit = lowPrio (if stdenv.hostPlatform.is32bit then stdenv else multiStdenv);
} |
@vcunat Hmm, I think the 32bit ld in "multi-lib stdenv" might still expand |
I marked this as stale due to inactivity. → More info |
Describe the bug
A clear and concise description of what the bug is.
Dynamic linking tokens can be put in the library path and ld.so is supposed to fill it in according to the executable's arch.
From to the manpage:
To Reproduce
Steps to reproduce the behavior:
$LIB
in place oflib
orlib32
in the library pathlib
, notlib32
This can be observed by looking at the paths in the log of
LD_DEBUG=libs
or infering it fromLD_PRELOAD
error messages:(I'm sure there are better methods.)
Expected behavior
A clear and concise description of what you expected to happen.
This would be expected behaviour with 64bit executables but with 32bit ones, it should be the other way around:
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
This popped up in #84686 while trying to update to 0.5.1 where Mangohud switched to a loading mechanism which relies on dynamic linking tokens.
Notify maintainers
@vcunat @jtojnar @edolstra @Ma27
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Maintainer information:
The text was updated successfully, but these errors were encountered: