You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if ldd is pointed at a dynamically linked executable for a different but compatible architecture (eg i686), it will claim the executable is not dynamically linked.
Steps To Reproduce
Steps to reproduce the behavior:
$ nix shell nixpkgs#{glibc,file}
$ nix build nixpkgs#pkgsCross.gnu32.hello
$ ldd result/bin/hello
not a dynamic executable
$ file result/bin/hello
result/bin/hello: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /nix/store/mnn74dhr6fcjl0iv7a1hvwvmyly3lq1a-glibc-i686-unknown-linux-gnu-2.38-27/lib/ld-linux.so.2, for GNU/Linux 3.10.0, not stripped
### Expected behavior
accurate error message
### Additional context
this is probably a glibc bug, but i didn't want to create a whole new account without being sure.
### Notify maintainers
<!--
Please @ people who are in the `meta.maintainers` list of the offending package or module.
If in doubt, check `git blame` for whoever last touched something.
-->
### Metadata
Please run `nix-shell -p nix-info --run "nix-info -m"` and paste the result.
```console
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here
Describe the bug
if ldd is pointed at a dynamically linked executable for a different but compatible architecture (eg i686), it will claim the executable is not dynamically linked.
Steps To Reproduce
Steps to reproduce the behavior:
Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: