I tried building the latest 1.0.1c source tree under win-x64 today, and there is a problem when using cygwin's perl. It looks like whoever built the perl scripts for the win-x64 platform made assumptions about the way perl handles file paths with windows-style backslashes "\" in them. Basically cygwin perl assumes that a backslash is a string escape sequence and the backslash is "lost", which obviously causes the build to fail in numerous places.
It counterproductive not to provide specific error messages. Anyway, poor interaction between native Win32 tools and Posix emulators such as cygwin is *not* limited to above problem. It's strongly recommended to use "matching" tools, i.e. if you use Microsoft nmake and compiler, use native Win32 Perl such as ActivePerl, if you use cygwin make and compiler, use cygwin perl, if you use MinGW, use MinGW perl... One can argue that it's unfortunate recommendation (because bugs win), but it's not insane requirement.
Perhaps the openssl devs consider this to be a bug in cygwin perl, rather than a bug in openssl's perl scripts. I am not an expert in Perl, so I am not in a position to provide a patch. This bug has probably already been reported and I'll get flamed for not having researched the open bug list. Oh well. P.S. I hate the picky error-prone retarded language also known as perl lol
Listen you yourself! We should celebrate the diversity, not call it names. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
