Re: [openssl.org #1693] Compiling OpenSSL with mingw-w64

[[EMAIL PROTECTED] via RT]

  Hi,

> > Please, could you propose a patch to the OpenSSL head.
> > In the head -lwsock32 is replaced by -lws2_32.

Here's a patch against today's snapshot of head.

> > I think that you has to compile with -DWIN32_LEAN_AND_MEAN in
> > Configure before to do some undefs in openssl headers.

I'm not really convinced, but for the time being, I've added that
compile
option to get rid of that more or less cosmetic issue.
Apart from adding a line to configure, I needed a slight modification
to apps/speed.c and engines/e_aep.c because mingw-w64 comes
with definitions for "pid_t" and "alarm" and in crypto/mem_cmp.c,
gcc complained about a (and b) being redefined as a different kind
of symbol, so I renamed the local symbols to have different names
from the parameters.

Regards,
 Stefan



openssl-HEAD.patch
Description: Binary data

Re: [openssl.org #1693] Compiling OpenSSL with mingw-w64

[[EMAIL PROTECTED] via RT]

  Hi,

> Please, could you propose a patch to the OpenSSL head.
> In the head -lwsock32 is replaced by -lws2_32.

Will do..

> I think that you has to compile with -DWIN32_LEAN_AND_MEAN in
Configure 
> before to do some undefs in openssl headers. Also see other win64
targets.

But doesn't that mean that any user of openssl wanting to use e.g.
X509_EXTENSIONS has to take care of that problem himself?
Also, x509.h is already undefining 2 of the 3 problematic symbols
anyway.
IMO that's something that really should be "fixed" in the headers.

Regards,
  Stefan


__
OpenSSL Project http://www.openssl.org
Development Mailing List   openssl-dev@openssl.org
Automated List Manager   [EMAIL PROTECTED]