Hey dude, built ok here, after some tweaks to my server code, all is sweet, send you the SSLeay binaries if u like... Pj.
----- Original Message ----- From: "Thomas J. Hruska" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 01, 2002 2:12 AM Subject: Re: Building openssl on Win2K > At 11:09 AM 10/31/2002 -0800, [EMAIL PROTECTED] writeth: > > 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 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: > > -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 > > 29 > >but that doesn't seem to impress cryptlib.c. > >At this point I started to get suspicious... > > If so, can I please hear from you as to how you managed the feat? > > If you just need a default build of OpenSSL for the Win32 Platform, check > out the Win32 OpenSSL Installation Project: > > <http://www.shininglightpro.com/search.php?searchname=Win32+OpenSSL> > > It comes with development libraries to link with (for VC++, Borland C++ > Builder 5 (3 & 4?), and MinGW), pre-compiled DLLs, and the entire > command-line toolset pre-built for programmers and end-users all in a > really nice, fast, and easy installation package for point-and-clickers. > > This project also cuts out many legal issues since your product can rely on > OpenSSL being installed, but not having to distribute binaries. For most > users, they can rely on the same code base you use to develop with (a > _HUGE_ plus when it comes to support for the product). Just point at the > Win32 OpenSSL Project when distributing your product. > > Hope this helps! > > > Thomas J. Hruska -- [EMAIL PROTECTED] > Shining Light Productions -- "Meeting the needs of fellow programmers" > http://www.shininglightpro.com/ > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
