Is there a utility that will examine a binary executable to determine what it's dependencies are (i.e external library requirements)?

I have a program that will run on one system, but on another it returns the following:

# ./project2
-sh: ./project2: not found

Does this mean that it can't find a required library? The file "project2" most cirtainly is there, and it is chmod 755 and I am root. (It would be nice if it reported what it couldn't find!)

- Joe

"Is there a utility that will examine a binary executable to determine what it's dependencies are (i.e external library requirements)?"

You can do it with rpm on an rpm based system like Fedora or Red Hat. First you find out what rpm package provides project2. Use the full pathname for project2 in this rpm command:

rpm -q --whatprovides /pathname/project2

Let's assume that rpm replies: utilpkg-1.0.2

Then you can find out what packages utilpkg-1.0.2 is dependent on with:

rpm -q -R utilpkg-1.0.2

----------------------
Steve Stites

No, this has nothing to do with RPMs. In my example, "project2" is the name of the executable I want to run. It does exist. But when I type
what I get in response is:
This looks like the file "project2" does not exist, but that simply is not the case:
What I think this means is that the executable itself is looking for a library that does not exist. I'd like to know how to find out what the executable is looking for.

- Joe

give "ldd" a try

ldd /usr/bin/executable

One more thing you can do is.... you can give the whole path and see.

E.g., if project2 is in /home/raseel :

$/home/raseel/project2 <Enter>