INTERNAL: How to Find Libraries That an Executable Depends On
Anonym
Topic:
On some UNIX systems like SunOS, Solaris or Linux to find the location of libraries that an executable depends upon, you can use the UNIX ldd command.
On IRIX the command is 'elfdump -Dl' (e.g. %elfdump -Dl idl).Discussion:
Using the ldd command on a binary executable will indicate all of the shared objects loaded as a result of running the executable. For example for sidl (IDL student version):
56 <ren~bin.solaris2.x86> pwd
/usr/local/rsi/idl_5sv/bin/bin.solaris2.x86
57 <ren~bin.solaris2.x86> ldd sidl
libidl.so.5 => ./libidl.so.5
libDtSvc.so.1 => /usr/dt/lib/libDtSvc.so.1
libtt.so.2 => /usr/dt/lib/libtt.so.2
libXm.so.3 => /usr/dt/lib/libXm.so.3
libXext.so.0 => (not found)
libXt.so.4 => /usr/lib/libXt.so.4
libX11.so.4 => /usr/lib/libX11.so.4
libsocket.so.1 => /usr/lib/libsocket.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libw.so.1 => /usr/lib/libw.so.1
libintl.so.1 => /usr/lib/libintl.so.1
libm.so.1 => /usr/lib/libm.so.1
libc.so.1 => /usr/lib/libc.so.1
libidl_cdf.so.5 =>> ./libidl_cdf.so.5
libidl_netcdf.so.5 => ./libidl_netcdf.so.5
libidl_hdf.so.5 => ./libidl_hdf.so.5
libMesaaux.so => ./libMesaaux.so
libMesatk.so => ./libMesatk.so
libMesaGLU.so => ./libMesaGLU.so
libMesaGL.so => ./libMesaGL.so
libXext.so.0 => /usr/openwin/lib/libXext.so.0
libmp.so.1 => /usr/lib/libmp.so.1
58 <ren~bin.solaris2.x86></ren~bin.solaris2.x86></ren~bin.solaris2.x86>
Solution:
[Edit this field in the IDL-based Tech Tip Editor, v3]</ren~bin.solaris2.x86>