Compiling OpenSSL shared libraries with custom name on Unix platforms

[shivaramakrishna chakravarthula]

Hi,

I have compatibility issues for my application with new versions of OpenSSL
and I want to use the older version of OpenSSL with my application. So, I
want to link my application with an OpenSSL library built with the custom
name so that it works fine on all systems and I can be assured of using the
desired OpenSSL version. I am using RPATH to locate the libraries in
runtime and I want to make sure my libraries don't conflict with existing
libraries.

Thanks,
Shiva

On Tue, 14 Jul 2020 at 16:31, Kenneth Goldman <kgoldman at us.ibm.com> wrote:

> > From: shivaramakrishna chakravarthula <shivaramakrishna.ch at gmail.com>
> >
> > Is it possible to compile OpenSSL shared libraries with custom
> > names on Linux/ Unix platforms to avoid conflicts with installed
> > OpenSSL libraries?
> > I have tried to modify the SHLIB_EXT in Configure script but it is
> > not working. I am sure it is a common problem and someone in this
> > group can help.
>
> If this is just for local testing, I typically build but don't
> install.  By changing my paths, I can use the local copy.
>
> If you're sure you have ABI compatibility, could you
> manually copy and rename the .so files to /usr/include,
> /usr/local/include  or equivalent?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mta.openssl.org/pipermail/openssl-users/attachments/20200714/8537bdc5/attachment.html>