Arthur Ramsey via RT
2014-10-19 18:15:59 UTC
I'm attempting to disable SSLv3 at build time with no-ssl3. This was
successful on Linux, but not on Windows. I'm building on Windows 7 with
VC 2008 and strawberry perl. It was successful with the following
procedure.
1.
%comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" x86_amd64
2.
Change to the directory containing openssl sources
cd C:\openssl-1.0.1j
3.
Configure the openssl build
perl Configure VC-WIN64A no-ssl2
4.
Prepare the target environment
ms\do_win64a
5.
Clean up previous compliation
nmake -f ms\nt.mak clean
6.
Build
nmake -f ms\nt.mak
7.
Test the build
nmake -f ms\nt.mak test
Once I add the no-ssl3 option, compilation of the 64-bit static library
fails with the following. I started fresh from the src dist with each
attempt.
Building OpenSSL
lib /nologo /out:out32\ssleay32.lib @C:\Users\arthurr\AppData\Local\Temp\nm96B5.tmp
link /nologo /subsystem:console /opt:ref /debug /out:out32\constant_time_test.exe @C:\Users\arthurr\AppData\Local\Temp\nm96D5.tmp
LINK : fatal error LNK1181: cannot open input file 'out32\ssleay32.lib'
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\x86_amd64\link.EXE"' : return code '0x49d'
Stop.
I see there was a fix for no-ssl3 in 1.0.1j, but it may still be an
issue with Windows builds? The error isn't descriptive, but perhaps a
openssl-dev could try reproducing the issue.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-***@openssl.org
Automated List Manager ***@openssl.org
successful on Linux, but not on Windows. I'm building on Windows 7 with
VC 2008 and strawberry perl. It was successful with the following
procedure.
1.
%comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" x86_amd64
2.
Change to the directory containing openssl sources
cd C:\openssl-1.0.1j
3.
Configure the openssl build
perl Configure VC-WIN64A no-ssl2
4.
Prepare the target environment
ms\do_win64a
5.
Clean up previous compliation
nmake -f ms\nt.mak clean
6.
Build
nmake -f ms\nt.mak
7.
Test the build
nmake -f ms\nt.mak test
Once I add the no-ssl3 option, compilation of the 64-bit static library
fails with the following. I started fresh from the src dist with each
attempt.
Building OpenSSL
lib /nologo /out:out32\ssleay32.lib @C:\Users\arthurr\AppData\Local\Temp\nm96B5.tmp
link /nologo /subsystem:console /opt:ref /debug /out:out32\constant_time_test.exe @C:\Users\arthurr\AppData\Local\Temp\nm96D5.tmp
LINK : fatal error LNK1181: cannot open input file 'out32\ssleay32.lib'
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\x86_amd64\link.EXE"' : return code '0x49d'
Stop.
I see there was a fix for no-ssl3 in 1.0.1j, but it may still be an
issue with Windows builds? The error isn't descriptive, but perhaps a
openssl-dev could try reproducing the issue.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-***@openssl.org
Automated List Manager ***@openssl.org