Difference between revisions of "Solving missing library problems"
From Notes_Wiki
m |
m |
||
| Line 13: | Line 13: | ||
Many times on x86_64 systems the library could be installed but it may be 64-bit version installed in /lib64 or /usr/lib64. To install equivalent version of library in /lib or /usr/lib, use yum to install same package with '<tt>i686</tt>' appended to name. For example, '<tt>libstdc++-devel.i686</tt>' Note that many times RPATH may include $ORIGIN which means relative to executables location. | Many times on x86_64 systems the library could be installed but it may be 64-bit version installed in /lib64 or /usr/lib64. To install equivalent version of library in /lib or /usr/lib, use yum to install same package with '<tt>i686</tt>' appended to name. For example, '<tt>libstdc++-devel.i686</tt>' Note that many times RPATH may include $ORIGIN which means relative to executables location. | ||
<yambe:breadcrumb>System_troubleshooting|System troubleshooting</yambe:breadcrumb> | |||
Revision as of 08:00, 27 August 2018
<yambe:breadcrumb>System_troubleshooting|System troubleshooting</yambe:breadcrumb>
Solving missing library problems
To find dynamic libraries requred by an executable use:
ldd <file_name>
To find out path where executable will look for library use:
readelf -d <file_name> | grep RPATH
Many times on x86_64 systems the library could be installed but it may be 64-bit version installed in /lib64 or /usr/lib64. To install equivalent version of library in /lib or /usr/lib, use yum to install same package with 'i686' appended to name. For example, 'libstdc++-devel.i686' Note that many times RPATH may include $ORIGIN which means relative to executables location.
<yambe:breadcrumb>System_troubleshooting|System troubleshooting</yambe:breadcrumb>
