-
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Michael Wojcik
Sent: Monday, November 18, 2019 5:29 AM
To: openssl-users@openssl.org
Subject: RE: Static linking libssl.a and libcrypto.a on Linux x64 fails
> From: Aijaz Baig [mailto:aijazba...@gmail.com]
>
> From: Aijaz Baig [mailto:aijazba...@gmail.com]
> Sent: Wednesday, November 13, 2019 19:58
> However my current concern here is meeting libSSL and libCrypto's
> dependencies on
> host libraries on Linux platform. For instance, when I talked about 'linking'
> errors
> with respect to symbols lik
> Actually, that is also the format and mechanism with Microsoft Win32 tools,
> they just use the DOS-like file name "foo.lib" instead of "libfoo.a" to
> maintain makefile compatibility with their older Intel OMF-based toolchains.
> The object files inside > the archive are in COFF format, as th
Thank you for the suggestion. Will try that.
Regarding the static library, the term 'linking' I used was more tongue in
cheek but nonetheless. However my current concern here is meeting libSSL
and libCrypto's dependencies on host libraries on Linux platform. For
instance, when I talked about 'link
On 13/11/2019 15:23, Michael Wojcik wrote:
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Aijaz Baig
Sent: Wednesday, November 13, 2019 01:45
I am trying to statically link libssl.a and libcrypto.a into a static library
of my own
which I will be using in an applicat
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Aijaz Baig
> Sent: Wednesday, November 13, 2019 01:45
> I am trying to statically link libssl.a and libcrypto.a into a static library
> of my own
> which I will be using in an application (Linux).
You can't link any
