Comment by 🚀 stack

Re: "binary file reported as 'no such file or directory' upon..."

./fasmlist: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked,
interpreter /lib/ld-linux.so.2, BuildID[sha1]=d85decb81a47920afb2e52c6215debdceaea3dfe,
 for GNU/Linux 3.2.0, not stripped

🚀 stack [OP]

2023-09-01 · 9 months ago

3 Later Comments ↓

🐙 norayr · 2023-09-01 at 23:14:

and what is the output of

file /bin/bash

or some other binary that runs?

also can you do ldd on both - the file that doesn't run and something that does?

🚀 stack [OP] · 2023-09-02 at 01:05:

I won't be able till tomorrow.

😈 dimkr · 2023-09-02 at 08:44:

dpkg --add-architecture i386 && apt update && apt install libc6:i386 should fix this, if this is Debian or a derivative like Ubuntu. This is the error you get when you run a 32-bit executable on a 64-bit OS but the 32-bit loader (part of glibc) is missing.

Original Post

🌒 s/Linux

binary file reported as 'no such file or directory' upon execution — This has to be the weirdest behavior ever. A small utility that works fine on my main machine was copied over to my Thinkpad, running identical XUbuntu. Fails on ThinkPad only I can ls it, permissions are fine, even HD and objdump look reasonable. When I try to invoke it from command line, bash reports that it does not exist. strace shows execve with correct path, craps with ENOENT (no such file or directory) It's like it...

💬 stack · 12 comments · 2023-09-01 · 9 months ago

-- Response ended

-- Page fetched on Sun Jun 2 16:06:50 2024