I have been using VS2008, but I have seen the same errors. Some of the things I have done to work around them include: 1. Using a version of wcecompat based upon http://www.ohloh.net/p/mauriceks_wcecompat/ 2. Pull a few select files from OpenSSL tips to the 1.0.1e branch that I am working on. Including: * crypto/bio/bss_fd.c * crypto/cryptlib.c * crypto/o_str.c * e_os.h * e_capi.c * util/pl/VC-32.pl - I also had to modify this a little to fit our build process With the exception of the perl script I've not had to change any openssl source files.
-Ike- John Eichenberger Principal Engineer: Sustaining Engineering: Intermec 425.265.2108 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave Thompson Sent: Saturday, November 16, 2013 5:37 PM To: [email protected] Subject: RE: OpenSSL v.1.0.1e and MSVC 2013 > From: owner-openssl-users On Behalf Of Igor Mironchik > Sent: Saturday, November 16, 2013 05:09 > I'm trying to compile OpenSSL with MSVC 2013. > > First error was that <strings.h> include file wasn't found, and I > comment the next line in crypto/o_str.c > > #if !defined(OPENSSL_IMPLEMENTS_strncasecmp) && \ > !defined(OPENSSL_SYSNAME_WIN32) && \ > !defined(NETWARE_CLIB) > // # include <strings.h> > #endif > Are you sure you configured correctly? I haven't done 1.0.1e yet, but all versions I have built with MSVC define OPENSSL_SYSNAME_WIN32 as one would expect, which causes that #if to be skipped. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [email protected] This message is intended only for the named recipient. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of this information is strictly prohibited.
