"Zot O'Connor" <[EMAIL PROTECTED]>:
> The docs reference CygWin32 and Mingw32. It *seems* both work, but they
> are not consistent. Specifically the perl Configure command in
> install.win32 doesn't mention how to run for pure Cygnus.
>
> The only differences I see between then is:
>
> "CygWin32", "gcc:-DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -m486
> -Wall:(unknown)::BN_LLONG $x86_gcc_des $x86_gcc_opts:",
> "Mingw32", "gcc:-DL_ENDIAN -fomit-frame-pointer -O3 -m486
> -Wall:(unknown):BN_LLONG $x86_gcc_des $x86_gcc_opts:",
>
> the -DTERMIOS and the (unknown):: vs. (unknown):
I can't comment on the lack of instructions for CygWin32, but the
Mingw32 configuration line is missing a colon (which resulted in less
efficient code, because the optimization flags were used as linker
flags).
Also I assume that all the Windows builds (at least the 32bit ones)
are suited for multi-threading by default (which means that that
"(unknown)" should really just be an empty string; all it does is
produce a warning while running Configure). Windows experts: Is this
assumption correct, or can there be problems? I'll remove them for
now.
While we're at it, I suppose we can now disable the automatic warning
about <foo.h> => <openssl/foo.h>, or should we wait until 0.9.4 has
been released because some may skip 0.9.3 and 0.9.3a?
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
