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 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 has > apparently changed since I first reported this. > > Any assistance, please? > > Thanks, > Tyrel > > > On Mon, Nov 28, 2011 at 9:45 AM, Tyrel Haveman <tyr...@gmail.com> wrote: > >> 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 1>MINFO >> perl util\mk1mf.pl nasm VC-WIN32 1>ms\nt.mak >> perl util\mk1mf.pl dll nasm VC-WIN32 1>ms\ntdll.mak >> perl util\mk1mf.pl nasm BC-NT 1>ms\bcb.mak >> >> All of the mk1mf.pl lines fail, however, with: >> no rule for crypto\modes\ghash-x86 at util\mk1mf.pl line 966. >> >> This failure is fairly recent (within the last two weeks). It was not >> happening previously. >> >> Any help or a fix would be much appreciated. >> >> Thanks, >> Tyrel >> >> >
