I use the OpenSSL libraries on Solaris and Linux and have recently hacked my copy of Makefile.org to create copies of the shared libraries libssl.so and libcrypto.so with different names (eg libxyzssl.so and libxyzcrypto.so) - note: the hack is minimal, just building _additional_ shared libraries as I found that trying to only produce the shared libraries with different names was a real headache that lead nowhere.
The rationale for this regretable action was to avoid my shipped product picking up other copies of the shared libraries on Solaris via the LD_LIBRARY_PATH mechanism. If someone had this environment variable set and executed my program and picked up copies of the OpenSSL shared libraries which had been compiled without thread support or with other options selected/deselected which my program relies upon, bad things may happen. I tried just renaming libssl.so to libxyzssl.so, however this causes a failure when the library is linked against as it still has the internal name libssl.so. I guess this the OpenSSL build process could allow specification of the shared library names during Configure. A shorter term goal may be to add _mt to the end of shared library names to differentiate between libraries built with or without thread support, as seen in some other product involving shared libraries. Regards, Daniel McLean [I recently sent this to the openssl-users list but got no reply - I suppose this is the more appropriate list for this feature request] -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
