ldd utility shows which shared object files a binary executable depends on, and also shows the path of that binary executable on the file system.
Is it possible to modify this path, on an existing executable? For example, suppose I have a binary "foo.so", and I say:
libssl.so.0.9.8 => /opt/lib64/libssl.so.0.9.8
If I deploy this
.so file to a machine that doesn't have
lbssl.so.0.9.8 at the specified path, I will of course get a linker error when using
foo.so. So, is it possible to modify the linkage path on an existing executable?
I realize another solution would be to ensure that the existing linkage path points to a valid object file actually copying the object file to the path that
ldd shows. But let's say I have a situation where that's not feasible to do. Is it possible to modify the linkage path on an existing executable?