OpenSSL 1.0.1 build fails on Windows with do_nasm
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
Re: OpenSSL 1.0.1 build fails on Windows with do_nasm
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 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 > >
Re: OpenSSL 1.0.1 build fails on Windows with do_nasm
Sorry, it is still line 966 of mk1mf.pl. On Fri, Dec 9, 2011 at 9:32 AM, Tyrel Haveman 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 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 >> >> >
Re: OpenSSL 1.0.1 build fails on Windows with do_nasm
> 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 for a while, and was refreshing it with 'cvs update', then you might end up in situation when crypto/modes/asm/ghash-x86.pl is not present in your tree. This would result in error message you are referring to. So just see if you have crypto/modes/asm/ghash-x86.pl and if not ... __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: OpenSSL 1.0.1 build fails on Windows with do_nasm
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 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. > > 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 for > a while, and was refreshing it with 'cvs update', then you might end up > in situation when crypto/modes/asm/ghash-x86.pl is not present in your > tree. This would result in error message you are referring to. So just > see if you have crypto/modes/asm/ghash-x86.pl and if not ... > __ > OpenSSL Project http://www.openssl.org > Development Mailing List openssl-dev@openssl.org > Automated List Manager majord...@openssl.org >
