Re: compat_linux failures due to execve, openat, etc.

[RVP <rvp%SDF.ORG@localhost>]

On Thu, 30 Oct 2025, Kevin Bloom wrote:

> When I view the ktrace(1) dump I see lines like:
>
> 13390  13390 nix-env  CALL execve(0x7f7fffffdec0, 0x7f7fff223a90, 0x7f7fff223ab0)
> 13390  13390 nix-env  NAMI "/nix/store/${hash1}-nix-2.32.2/bin/nix-env"
> 13390  13390 nix-env  NAMI "/emul/linux"
> 13390  13390 nix-env  NAMI "/emul/linux/nix/store/${hash2}-glibc-2.40-66/lib/ld-linux-x86-64.so.2"a
> 13390  13390 nix-env  NAMI "/nix/store/${hash2}-glibc-2.40-66/lib/ld-linux-x86-64.so.2"
> 13390  13390 nix-env  EMUL "linux"
> 13390  13390 nix-env  RET execve -1 errno -2 No such file or directory
>
> When I look in the glibc directory I do see that shared lib in there
> so I'm confused why it's saying it's missing.

That `XXX/lib/ld-linux-x86-64.so.2' is actually a symlink pointing to
`XXX/lib64/ld-linux-x86-64.so.2', right? Is the symlink pointing to an existing
file, or have you copied the file in place of the symlink itself?

-RVP