All, On 6/18/14, 1:58 PM, Christopher Schultz wrote: > I'm getting a lot of crypto-related build (not link) errors, so I'll > have to follow-up on those.
Okay, so it seems that OpenSSL's include file is ... broken. C:\Users\IEUser\Desktop>type %MYTEMP%\build\openssl-1.0.1h\include\openssl\openslv.h ../../crypto/opensslv.h That's not a valid C header file. It comes right out of the OpenSSL source distribution, and its used by tcnative directly. All kinds of compiler errors are thrown when that gets included from include/ssl_private.h The file OPENSSL_HOME/include/openssl/../../crypto/opensslv.h does contain a legitimate C header file. I checked on my Mac and a Linux box and I can confirm that /usr/include/openssl/opensslv.h contains what the ../../crypto/opensslv.h file referenced above contains. It seems that the OpenSSL source package contains symlinks. I haven't found a command-line tar program on win32 that can expand an archive containing symlinks. This is getting frustrating. :( -chris
signature.asc
Description: OpenPGP digital signature
