From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.4.16 + ia64-011128: Unable to execute a "rwx" program
Date: Sat, 05 Jan 2002 05:06:51 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805747@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805720@msgid-missing>
>whale% ./prog
>zsh: no such file or directory: ./prog
This usually means that the program specifies an interpreter, and the
interpreter can not be found.
For a shell script, the interpreter is in the first line. For instance,
if I create a shell script called prog, and put in it two lines
#!/bin/foo
exit 0
and then run it, I get the error "bash: ./prog: no such file or directory".
The missing file is "/bin/foo" not "prog".
For an ELF executable, the interpreter is stored in the PT_INTERP field.
"readelf -l prog" will print out the value of the PT_INTERP field along
with a bunch of other stuff.
On my system, readelf -l /usr/bin/zip prints out
INTERP 0x0000f4 0x080480f4 0x080480f4 0x00013 0x00013 R 0x1
[Requesting program interpreter: /lib/ld-linux.so.2]
>This is a c++ program I compiled with the Intel compiler.
My guess is that you have an old OS with a new executable, or an old
executable with a new OS, in which case the executable is looking
for different version of ld.so than the one that comes with the OS.
Another possibility is that you are missing one of the libraries that comes
with the Intel compiler. Or perhaps, you need an environment variable set
before it will work correctly.
Jim
next prev parent reply other threads:[~2002-01-05 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 9:45 [Linux-ia64] 2.4.16 + ia64-011128: Unable to execute a "rwx" program Ville Herva
2002-01-05 5:06 ` Jim Wilson [this message]
2002-01-05 10:41 ` Ville Herva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698805747@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox