ssh: /linux2/lib/libcrypto.so.1.0.0: no version information available (required by ssh)

[cekees]

This is not a big deal, but I get these warnings whenever I use git and happend to have my LD_LIBRARY_PATH pointing to a hashstack profile containing libcrypto.

[certik]

This is a big deal (you just got lucky the symbols matched, but they don't need to if we upgrade the libcrypto in Hashstack so that it is not compatible with your system version anymore) and the reason why you should not use LD_LIBRARY_PATH. Why do you need to set LD_LIBRARY_PATH to point to a Hashstack profile? I don't, things are setup properly using RPATH.

So this looks like a bug that some packages do not setup their RPATH properly, and if so, you should just report which packages do that, so that we can fix them.

[cekees]

OK. I'll check to see if I've still got any issues without LD_LIBRARY_PATH. I was raising this partly because I thought we may need to include some additional flags to include the version information in libcrypto.