Ok. Got it. Thanks
On Wed, Nov 6, 2019 at 1:41 PM Brice André wrote:
> Then it means you properly compiled SSL in static.
>
> Regarding my first point, what I mean is that : if you statically link
> your libApp.so with ssl library, it will no need any dynamic library
> dependencies, which is
Sorry, but you are wrong : using libSSL.a in your libApp.so library does
not prevent you from using libSSL.so elsewhere in your program. In such
case, your program would still need libSSL.so
Le mer. 6 nov. 2019 à 09:38, Jakob Bohm via openssl-users <
openssl-users@openssl.org> a écrit :
>
Regarding #1: Using libSSL.a instead of libSSL.so should avoid using
libSSL.so by definition. Otherwise something went seriously wrong
with the linking. Same for any other library.
On 05/11/2019 18:22, Aijaz Baig wrote:
Thank you for the information.
I will address your points here:
1. I was
Then it means you properly compiled SSL in static.
Regarding my first point, what I mean is that : if you statically link your
libApp.so with ssl library, it will no need any dynamic library
dependencies, which is probably what you want. But your libApp.so will be
loaded by a program. If this
ldd libAPP.so does NOT have any reference to libSSL.so or for that matter
any SSL library. Which is why I had to use nm to check for SSL related
symbols
On Mon, Nov 4, 2019 at 6:31 PM Floodeenjr, Thomas <
thomas_floodee...@mentor.com> wrote:
> To check if you are linked statically or
Thank you for the information.
I will address your points here:
1. I was not aware of the fact that only those symbols that have been used
get imported when linking a library statically. So that very well could be
the case. I didn't get what you mentioned about the static linking
preventing the
To check if you are linked statically or dynamically, what does ldd tell you?
(ldd libAPP.so) Your library should not have a dependency on libssl.so or
libcrypto.so if you are linked statically.
-Tom
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Aijaz Baig
Sent:
Hello,
It's not an open-ssl issue, but more a compiler specific one.
With info you provided, I cannot tell you what you get as results, but two
points that may help:
1. regarding the 87 ssl symbols : when you link with a library, only the
useful symbols are imported. So, if the code in
