I'm trying to use shared libraries that don't play well with the ld-linux-x86-64.so.2 that is found in /lib64. I don't have root access so I can't change the file in /lib64. Is there a way that I can tell my RHEL5.7 box to use a different ld-linux-x86-64.so.2? I've tried putting the path to the version that I need to use inside $LD_LIBRARY_PATH, but it gets ignored there.
I have an executable that came packaged with some shared libs. The executable mostly works with the libraries that are already found on the machine, but every once in a while crashes and points to one of the libraries that I'm using from /lib. When I add some of the libraries that came with the executable to my LD_LIBRARY_PATH, it causes segmentation faults for simple commands like 'ls' 'cp' 'ldd' A version of the ld-linux-x86-64.so.2 also came with this executable and it doesn't cause a seg fault when I run the command ./ld-linux-x86-64.so.2 --list libc.so (or the other library that causes commands to break). I wanted to be able to test out using the ld-linux-x86-64.so.2 that came packaged with the software to make sure that that took care of the issues (and didn't cause others) before going to IT and having them make changes to all of the boxes that we'll run the software on. Or if possible build the work around into my job script so that I don't have to go through the whole change request process.
One sympton of the included libc.so not playing well with ld-linux.so is when I try doing a command is as follows. *cp: relocation error: libc.so.6: symbol _dl_tls_get_addr_soft, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference* I am the only one that uses my machine, but my company won't give out root access to users because the way the network is set up if you've got root on one linux box you've got it on all of them.