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"
but the gcc linker failed to find the openssl functions.
Anyone have any ideas?
We have been using OpenSSL for Windows (x64) built with MinGW for a long
time.
Can you send your linker command. What from the OpenSSL64/lib
directory do you link to?
Below is your compiler command, but it's my linker that's failing.
compiler: gcc.exe -m64 -DWINVER=0x0501 -D_WIN32_WINNT=0x0501
-D_WIN32_IE=0x0501 -DPTW32_STATIC_LIB -D__CLEANUP_C -m64 -O2 -pipe
-mms-bitfields -fno-builtin -march=core2 -mtune=core2 -DL_ENDIAN
-DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2
-DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m
-DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM
-DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM
-DECP_NISTZ256_ASM -DX25519_ASM -DPADLOCK_ASM -DPOLY1305_ASM
-DWINVER=0x0501 -D_WIN32_WINNT=0x0501 -D_WIN32_IE=0x0501
-DPTW32_STATIC_LIB -D__CLEANUP_C -DUNICODE -D_UNICODE
-DWIN32_LEAN_AND_MEAN -DOPENSSL_SSL_CLIENT_ENGINE_AUTO=capi
-DOPENSSL_CAPIENG_DIALOG -m64 -pipe -mms-bitfields -fno-builtin
-march=core2 -mtune=core2 -D_MT -DZLIB -DNDEBUG -I/mingw/include
@Ken: this seems to be a quite old thread, but if you need either the
include files or the .a files
or both, we could email them to you.
I have the include files.
I think I need the .a files or equivalent, but I prefer to use the
Shining Light install. If I get a private copy from you, I have to
distribute it.
Besides the process and legal issues, it doesn't feel right to
distribute security code that I got via email from an unknown
person with the email name 'sfhacker'. :-)
