> From: Michael Wojcik
> Without picking at the problem files myself, not really. It's
> probably something that will be fairly obvious in retrospect but I'm
> not seeing it from here.
>
> The import libraries (I'm assuming libssl.lib is one as well, on
> your system) basically tell the linker "
> "c:/program files/mingw/bin/gcc.exe" -D_MT -DTPM_WINDOWS -I. -shared -o
> libibmtss.dll tssfile.o tsscryptoh.o tsscrypto.o tssprintcmd.o tss.o
> tssproperties.o tssmarshal.o tssauth.o tssutils.o tsssocket.o tssdev.o
> tsstransmit.o tssresponsecode.o tssccattributes.o tssprint.o Unmarshal.o
> Com
On 3/22/2019 12:18 PM, Michael Wojcik wrote:
I seem to have discarded some of your older messages. Did you ever
send us the actual link command that's being used? Maybe that will
throw some light on the problem.
"c:/program files/mingw/bin/gcc.exe" -D_MT -DTPM_WINDOWS -I. -shared -o
libibmts
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Ken Goldman
> Sent: Thursday, March 21, 2019 13:44
> To: openssl-users@openssl.org
>
> On 3/20/2019 12:41 PM, Michael Wojcik wrote:
>
> >
> > Sounds like you might have import libraries there. Does "ar t
> > libcrypto.l
On 3/20/2019 6:44 PM, Sergio NNX wrote:
I've been happily using the Shining Light 32-bit binaries with both
openssl 1.0 and 1.1 and mingw.
Getting back to this:
I tried mingw linking against these
"c:/program files/openssl64/lib/libcrypto.lib"
"c:/program files/openssl64/lib/libssl.lib"
On 3/20/2019 12:41 PM, Michael Wojcik wrote:
Sounds like you might have import libraries there. Does "ar t
libcrypto.lib" show a bunch of .obj members, or a bunch of .dll
members? If it's the latter, then it's just an import library that
tells the linker what DLL needs to be loaded at runtim
>> I've been happily using the Shining Light 32-bit binaries with both
>> openssl 1.0 and 1.1 and mingw.
a) Where can we download OpenSSL binaries (x64) for Windows built with MinGW?
[ https://slproweb.com/products/Win32OpenSSL.html ]
b) D:\Temp-Apps\OpenSSL-Win64\bin>openssl version -a
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Ken Goldman
> Sent: Wednesday, March 20, 2019 08:46
> To: openssl-users@openssl.org
> Subject: Re: Using (not building) openssl with mingw on Windows 10
>
> On 10/29/2018 7:18 AM, Jakob Bohm vi
On 10/29/2018 7:18 AM, Jakob Bohm via openssl-users wrote:
On 26/10/2018 23:08, Ken Goldman wrote:
I've been happily using the Shining Light 32-bit binaries with both
openssl 1.0 and 1.1 and mingw.
On a new machine, I tried the 64-bit binaries. However, they're
missing the openssl/lib/mingw
On 26/10/2018 23:08, Ken Goldman wrote:
I've been happily using the Shining Light 32-bit binaries with both
openssl 1.0 and 1.1 and mingw.
On a new machine, I tried the 64-bit binaries. However, they're
missing the openssl/lib/mingw directory where the .a files resided.
It looks like the li
I've been happily using the Shining Light 32-bit binaries with both
openssl 1.0 and 1.1 and mingw.
On a new machine, I tried the 64-bit binaries. However, they're missing
the openssl/lib/mingw directory where the .a files resided.
It looks like the link procedure changed. Any hints before I
11 matches
Mail list logo
