I'm still having this build problem on Windows, with code just pulled
from CVS 1.0.1 stable branch. It happens when building the 32-bit build
on a 64-bit OS.
I think it depends on what do you mean by code just pulled from CVS
1.0.1 branch *exactly*? If you have a checked out tree, and had it
Thanks Andy. It looks like that was indeed the problem -- my copy of the
CVS tree had gotten out of sync somehow.
On Mon, Dec 12, 2011 at 7:29 AM, Andy Polyakov ap...@openssl.org wrote:
I'm still having this build problem on Windows, with code just pulled
from CVS 1.0.1 stable branch. It
I'm still having this build problem on Windows, with code just pulled from
CVS 1.0.1 stable branch. It happens when building the 32-bit build on a
64-bit OS.
Note that I can build the FIPS 2.0 module just fine before I build this.
It's now referring to line 973 instead of 966 in mk1mf.pl as it
Sorry, it is still line 966 of mk1mf.pl.
On Fri, Dec 9, 2011 at 9:32 AM, Tyrel Haveman tyr...@gmail.com wrote:
I'm still having this build problem on Windows, with code just pulled from
CVS 1.0.1 stable branch. It happens when building the 32-bit build on a
64-bit OS.
Note that I can build
I'm running the following commands on Windows with the latest code from the
1.0.1 branch:
set FIPSDIR=..\dep
perl Configure fips no-hw VC-WIN32 --prefix=c:\devel\openssl\out
call ms\do_nasm
The do_nasm script runs:
perl util\mkfiles.pl 1MINFO
perl util\mk1mf.pl nasm VC-WIN32 1ms\nt.mak
