Error while loading shared libraries | Cannot open shared object file | Library not found

[gtdang]

How do I solve these types of errors?

Error while loading shared libraries

Cannot open shared object file

Library not found

[gtdang]

Many programs are compiled with dynamic linking to libraries on which they depend. The dynamic linker called ld looks for these dependencies during run time and complains if it can't find them.

Example:

libmpichcxx.so not found

Here, it is looking for a library which is part of MPI implementations. You can load a module like mvapich2 so that the path to this library is added to LD_LIBRARY_PATH and can be found by the run time linker. It might happen that only a particular version is required. A web search on the library name also might reveal what software package it belongs to.

If you want to know what all shared libraries are required during run time by an executable, you can use the ldd utility. For example:

    $ ldd /gpfs/runtime/opt/paraview/4.2.0/bin/paraview
  linux-vdso.so.1 =>  (0x00007fffecfff000)
  /usr/local/lib/libslurm.so (0x00007f70f8348000)
  libc.so.6 => /lib64/libc.so.6 (0x0000003e18800000)
  libdl.so.2 => /lib64/libdl.so.2 (0x0000003e19000000)
  libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003e19400000)
  /lib64/ld-linux-x86-64.so.2 (0x0000003e18400000)

We generally make it a point to add information about these dependencies to the modules such that the info is displayed while loading modules. If you find a package for which dependencies are not displayed while loading modules or you are not able to figure out where to find the library file, contact us at [email protected] and we will correct the mistake.