Portal Home > Knowledgebase > Articles Database > Checking versions of library/so files?
Posted by CiscoMike, 04-14-2009, 06:19 PM Different problem than my earlier thread: http://www.webhostingtalk.com/showthread.php?t=854477 I freely admit this is something that is self inflicted as I made the mistake of trying to install OpenSSH from source on my own despite me knowing that OpenSSL was kinda goofy (as in I had 0.9.8g and 0.9.8i libraries all over the place). I know that I have OpenSSL 0.9.8k installed and working. PHP and Apache are both reporting that they are using the k release. I'm good there. However cURL and proftpd are still linking to the g release libraries and for the life of me, I cannot find where these buggers are. ld.so.conf is pointed at the newer libraries in /usr/local/lib and /usr/local/ssl/lib and I re-ran ldconfig to make sure. Is there a way to verify a version of the library/so files because this is killing me. I'm kinda like Monk (USA TV) only instead of germs, I'm freaked out by lame libraries and includes. edit: what I *think* is happening, based on the timestamps, is that cURL and proftpd are using the libraries in the /usr/lib64 directory instead of /usr/lib. What I don't get is when I make;make install, why things are only going into /usr/lib and /usr/local/lib and not into the /usr/lib64 directory despite my ./config stating that the libraries are being built for x86_64. Is it as simple as copying things over? Last edited by CiscoMike; 04-14-2009 at 06:29 PM. Reason: added more info...
Posted by CiscoMike, 04-14-2009, 06:59 PM The highlighted/underlined ones are where I think I have a problem, these are all from my ldconfig cache. In the cases of /usr/lib64/libcrypto.so.0.9.8 and /usr/lib64/libssl.so.0.9.8, could I copy (or symlink to) from the same files in /usr/local/lib or /usr/lib? Or is there a better way to clean out my ldconfig cache to remove those entries?
Add to Favourites Print this Article