It would be easier to help if we knew, for example, what platform you're on, what modules (you think) you have installed, how exactly you installed them, whether there were any errors at build/install time, etc.

In general, for tracking down problems with dependent libs, ldd is your friend (assuming you're on Linux/Unix — though there are similar tools for Windows). For example, if you have Crypt::SSLeay installed, find Crypt/SSLeay/SSLeay.so, and run ldd on it. It should list what other shared libraries SSLeay.so depends on, and whether (and from where) those other libraries (such as libssl.so) would be loaded.