New answers tagged libraries
The system will search first within LD_LIBRARY_PATH and then in the paths specified in /etc/ld.so.conf.
It is possible that the library path might be hard coded in the binary. From the RPATH Wikipedia Page The dynamic linker of the GNU C Library and its derivative Embedded GLIBC implement a rather complicated algorithm for searching for shared libraries. The basic search order is: The (colon-separated) paths in the DT_RPATH dynamic section ...
That is not tested, this is just what I would try. So I don't know if it can count as an answer. If you manage to trace the excution with a debugger (this is a work of patience). Once you have noted the addresses of the function you want to run. You can perhaps remote-control the debugger by the mean of a script. Beware that most applications must to go ...
This can be done in special cases. What you describe is something like dynamically loading plugins via the C dynamic linking loader: try man dlopen for details on that. Usually the code so called has to be compiled as "position independent", so you're almost certainly out of luck for any specific program. You could look at userland exec code for some hints ...
Based on the output, you're mixing i686 and i386 packages together. You need to take care that you have the appropriate archiecture (i386, i686, x86_64, etc.) for your system's hardware and the other packages you have installed. So in your case yum is correctly complaining that you don't have the i386 versions of the dependencies installed already. Error: ...
Add /usr/local/lib to /etc/ld.so.conf and run ldconfig, then you'll have this path added as a default path for libraries.
Allowing LD_LIBRARY_PATH for suid binaries like sudo is a security problem, thus LD_LIBRARY_PATH gets stripped out of the environment. sudo by default doesn't passthrough LD_LIBRARY_PATH to its children either for the same security concerns: carefully crafted libraries would allow you to bypass the sudo argument restrictions to execute whatever you want. If ...
Your configuration seems ok to me (you normally only have to override the sensible defaults in ./configure), you would normally include the build step (make). From the FAQ file included in the downloaded 1.2.8 archive: 13. How can I make a Unix shared library? By default a shared (and a static) library is built for Unix. So: make distclean ...
There is an issue in Chromium tracker to remove runtime dependency on libudev.so.0. It includes some useful information as well, see this link. Google Chrome installer creates symlink when needed, see this link.
Top 50 recent answers are included