Ooops--Guess that's what i get for trying to do this at 430AM. I'd think that INSTALL.W32 should be changed to reflect the new default output directory in the "test" section from: ********* * You can now try the tests: > cd out > ..\ms\test ********* to ********** > cd out32dll /*or whatever your output directory may be*/ > ..\ms\test ********** I'd tend to believe most people dont muck with their output dir on win32 After fix of signed/unsigned int warning in s3_pkt.c build completes w/out errors/warnings tests run to completion NT4/SP5 VC++6 E:\openssl-0.9.5beta1>cl Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86 E:\openssl-0.9.5beta1>link Microsoft (R) Incremental Linker Version 6.00.8168 Configure VC-WIN32 no Assembler (i.e. ms\do_ms) nmake ms\ntdl.mak Andrew Andrew -----Original Message----- From: Ulf Moeller <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Friday, February 25, 2000 11:51 AM Subject: Re: 0.9.5b1 Win32 Minor fix >On Fri, Feb 25, 2000, Andrew W. Gray wrote: >> change line 5 >> >> PATH=..\ms;%PATH% >> >> to reflect output directory for w32 build: >> >> PATH=..\out32dll;%PATH% > >That won't work. > >You should run test.bat in the output directory. > >(It would make sense to have test.bat change to that directory >automatically, but it may have different names e.g. out32dll or >out. Does command.com have a function to test for the existence >of a directory?) > >______________________________________________________________________ >OpenSSL Project http://www.openssl.org >Development Mailing List [EMAIL PROTECTED] >Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
