On 3/22/2010 5:10 PM, Andy Polyakov wrote: >>>> The nasmw.exe file no longer exists. The program is now distributed as >>>> simply nasm.exe and the build files should be adjusted in 1.0 and 0.9.8 >>>> branches to reflect this. >>> ??? The issue was addressed in 0.9.9 and 1.0 a while (like two years) >>> ago. VC-32.pl checks for both nasm and nasmw and pick newest version >>> among them. >> >> Which happens to be worthless since this is not part of the permitted >> build >> steps for FIPS. > > There is nothing one can do about that and renaming/copying nasm.exe > binary to nasmw.exe is the only solution regardless whether or not it > was already solved in 0.9.8 and 1.0. A.
Rename it to nasm.exe across the board, already, so it is fixed before another FIPS package is considered for validation. Well over two years and we still have this antique, and now we would be seeing 1.0.0 shipping with nasmw name support? Zany ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
