In fact it is the copy used by python, located at http://svn.python.org/projects/external/openssl-1.0.0a
I made a seach for "nasmw" inside the entire code an discovered that: /ms/bcb.mak /ms/nt.mak /ms/ntdll.mak All of these files do contain references to 'nasmw', and only. I observed that only Python's openssl repository do contain these files, so in this case it is a Python bug and requested the reopening of http://bugs.python.org/issue7280 If would be nice if you could add your comments there regarding the best approach on solving this. Sorry for misplacing this bug to openssl. -- /sorin http://blog.i18n.ro On Mon, Sep 13, 2010 at 17:03, Andy Polyakov via RT <[email protected]> wrote: > Hi, > >> Current version of nasm is 2.09 and it does not have the nasmw >> executable anymore, the correct executable is >> "nasm" and not "nasmw". I'm not sure when this happened but it was >> long time ago. >> >> Please repair the problem by >> * replace calls of nasmw with nasm > > OpenSSL checks for availability of both and picks newest one found. I.e. > if there is nasm, then it will use nasm. If it doesn't work for you, > then your source tree is either too old, or something is crazy about > your environment. In either case you should provide exact versioning > information and details about the actual problem [such as build log]. A. > > > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
