When I am not able to get any result to find a required packagege location by which command ...

# which bash
no bash in /usr/bin /usr/sbin /sbin

Then we should get immediate doubt as whether it is installed or not ?
If it is installed "man" command should show up. If man command it is shown it means that packge required is hidden.

Then "swlist" command osme times helps in finding the package, some times it confuses with man alternatives.

The best is to go to "/ " and do a find which should return us the required path,


# find . / -name ldd
./usr/ccs/bin/ldd

So ldd is installed in /usr/ccs/bin
To make it work
run this


# export PATH=$PATH:/usr/ccs/bin/
# ldd
usage: ldd [-d] [-r] [-s] [-v] [-y[,symbol]] files ...

[-d] check reference to data symbols
[-r] check reference to data and code symbols
[-s] display the search path used to locate the shared libraries
[-v] display all dependency relationships
[-y[,symbol]] display symbol resolutions

Hope this helps to find ldd installed path for u ..
What is ldd ?
ldd is a command that can list the dynamic dependencies of incomplete executable files or shared libraries.

ldd lists verbose information about dynamic dependencies and symbol references. If the object file is an executable file, ldd lists all shared libraries that would be loaded as a result of executing the file. If it is a shared library, ldd lists all shared libraries that would be loaded as a result of loading the library.

Examples :
If we want to know all the dependencies of a particular binary say "nco_t_tl1" we can use is this command as follows


# ldd -s nco_t_tl1

find library=/usr/lib/libdld.2; required by nco_t_tl1
/usr/lib/libdld.2 => /usr/lib/libdld.2

find library=/usr/lib/libc.2; required by implicit load
/usr/lib/libc.2 => /usr/lib/libc.2

find library=/usr/lib/libdld.2; required by /usr/lib/libc.2
/usr/lib/libdld.2 => /usr/lib/libdld.2

find library=/usr/lib/libc.2; required by nco_t_tl1
/usr/lib/libc.2 => /usr/lib/libc.2

find library=/usr/lib/libcl.2; required by nco_t_tl1
/usr/lib/libcl.2 => /usr/lib/libcl.2

find library=/usr/lib/libisamstub.1; required by /usr/lib/libcl.2
/usr/lib/libisamstub.1 => /usr/lib/libisamstub.1

find library=/usr/lib/libdld.2; required by /usr/lib/libcl.2
/usr/lib/libdld.2 => /usr/lib/libdld.2

find library=/usr/lib/libm.2; required by nco_t_tl1
/usr/lib/libm.2 => /usr/lib/libm.2

find library=/usr/lib/libCsup.2; required by nco_t_tl1
/usr/lib/libCsup.2 => /usr/lib/libCsup.2

find library=/usr/lib/libstream.2; required by nco_t_tl1
/usr/lib/libstream.2 => /usr/lib/libstream.2

find library=/usr/lib/libstd.2; required by nco_t_tl1
/usr/lib/libstd.2 => /usr/lib/libstd.2

By default ldd prints a simple dynamic path information. This consists of the dependencies recorded in the executable (or the shared library) followed by the physical location where these libraries are found.

ldd a.out
./libx.so => ./libx.so
libc.so => /usr/lib/hpux32/libc.so.1
libdl.so => /usr/lib/hpux32/libdl.so.1

The -v option causes ldd to print dependency relationship along with the dynamic path information.

ldd -v a.out
find library=./libx.so; required by a.out
./libx.so => ./libx.so
find library=libc.so; required by a.out
libc.so => /usr/lib/hpux32/libc.so.1
find library=libdl.so; required by /usr/lib/hpux32/libc.so.1
libdl.so => /usr/lib/hpux32/libdl.so..1

The -r option to ldd causes it to analyze all symbol references and print information about unsatisfied code and data symbols.

./libx.so => ./libx.so
libc.so => /usr/lib/hpux32/libc.so.1
libdl.so => /usr/lib/hpux32/libdl.so.1
symbol not found: val1 (./libx.so)
symbol not found: count (./libx.so)
symbol not found: func1 (./libx.so)

Do you like this article? Share It!