Okay, I give up.
I followed the build instructions in INSTALL.W32 for VC++ only to find an unparseable makefile (ntdll.mak) with carriage returns embedded in the names of two macros (e.g. SSL^MOBJ=$(OBJ_D)\ssl.obj ...). When I fixed that, I discovered that the makefile was attempting to copy files from the $(SRC_D) (".") directory that actually lived in its many subdirectories. Rather than perform the major surgery required to fix that gaff, I decided to fall back, regroup and try plan B, building under Cygwin. That got me as far as the first call to gcc: gcc -I. -I../include -DTHREADS -DDSO_WIN32 -DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O2 -m486 -Wall -c -o cryptlib.o cryptlib.c cryptlib.c:105: #error "Inconsistency between crypto.h and cryptlib.c" cryptlib.c checks for #if CRYPTO_NUM_LOCKS != 29 # error "Inconsistency between crypto.h and cryptlib.c" #endif Of course, crypto.h says #define CRYPTO_NUM_LOCKS 29 but that doesn't seem to impress cryptlib.c. At this point I started to get suspicious... So my question is - is there anyone who has successfully built openssl-0.9.6g on any Win32 platform? If so, can I please hear from you as to how you managed the feat? Thanks, -Nick
|
- to secure a directory Karim
- to secure a directory Karim
- OpenSSL and Onboard Private Key Processin... Melbourne Barton
- to secure a directory Karim
- Re: Building openssl on Win2K openssl . 1 . nburkitt
- Re: Building openssl on Win2K Gait Boxman
- Re: Building openssl on Win2K Noel Burton-Krahn
- Re: Building openssl on Win2K Tim Regovich
- RE: Building openssl on W... openssl . 1 . nburkitt
- Re: Building openssl on Win2K Thomas J. Hruska
- Re: to secure a directory Adriano Devillaine
- Re: to secure a directory karim bernardet