> crypto\x86cpuid.pl win32n /MT /Ox /O2 /Ob2 -DOPENSSL_THREADS -DDSO_WIN32 > -W3 > -WX -Gs0 -GF -Gy -nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN > -DL_ENDIAN -D_CRT_SECURE_NO_DEPRECATE -DOPENSSL_BN_ASM_PART_WORDS > -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM > -DMD5_ASM -DRMD160_ASM -DAES_ASM -DWHIRLPOOL_ASM -DOPENSSL_NO_IDEA > -DOPENSSL_NO_RC5 -DOPENSSL_NO_MD2 -DOPENSSL_NO_MDC2 -DOPENSSL_NO_KRB5 > -DOPENSSL_NO_JPAKE -DOPENSSL_NO_DYNAMIC_ENGINE >tmp32\x86cpuid.asm > Access is denied. > NMAKE : fatal error U1077: 'crypto\x86cpuid.pl' : return code '0x1' > Stop. > > Looks like it wants to execute a Perl script? That probably doesn't work > that way on Windows...
Unfortunately, it does... OpenSSL requires Perl to build it on Windows. And indeed, the build slave does have perl installed: Found a working perl at 'c:\Perl\bin\perl.exe' Found an SSL directory at '..\..\openssl-1.0.0a' However, since Christian Heimes last changed it, we are not passing PERL anymore into the makefile, so this broke. In the past, we didn't need Perl on the slaves, anyway, since our external copy of OpenSSL had OpenSSL already pre-configured, and all Perl-generated files were included. In 1.0.0, OpenSSL started to generate assembler files with Perl, which broke the build. I have now added them to the external copy as well, so this is fixed. Now, the XP build succeeded. For some reason, the Windows 7 build failed due to duplicate symbols. I have cleaned the build area, and it currently retries. Regards, Martin _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
