Re: Phantom executables

[Steven Smith <sos22@cam.ac.uk>]

[-- Attachment #1: Type: text/plain, Size: 933 bytes --]

> [brownh@langhans tex2rtf]$ ./163nogui
> bash: ./163nogui: No such file or directory
> [brownh@langhans tex2rtf]$ ls -l 16*
> -rwxrwxrwx    1 brownh   brownh     196812 Mar 26 16:20 163nogui
> 
> and, for an executable script test file in the same directory:
> 
> [brownh@langhans tex2rtf]$ ./test-executable
> I am executing this file
> 
> Is this a sign that I need to include an older libc library? 
Usually. The most common cause of this is a funny dynamic linker.
Try going:

readelf -l ./153nogui

and look for a line something like

[Requesting program interpreter: /lib/ld.so.1]

If you don't have the interpreter in the right place, you'll get
No such file or directory errors. The easiest way is then probably
to recompile the broken program, or failing that use an old libc.

If you do have the interpreter, or readelf can't find it, I'd be
somewhat confused.

Steven Smith,
sos22@cam.ac.uk.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]