Does the right thing on the current release.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
As for Doug's suggestion for separate targets. I'd argue against. It's
probably more appropriate to fix it up in ./Configure, e.g. by looking
at 'gcc --target-help' and removing [or adding] -mno-cygwin. A.
http://cvs.openssl.org/chngview?cn=20110. a.
i stand corrected about -mno-cygwin, it does seem great and i can
understand why one would want not letting go of it.
it's hard to find info about it on cygwin.com, but searching through
their mailing list archives, there are tons of messages evocating it.
some dating from year 2000 were
i'm not
sure how people are still able to use it from Cygwin; all i get if i do
a simple ./Configure mingw then make is:
gcc: The -mno-cygwin flag has been removed; use a mingw-targeted
cross-compiler.
then it errors out before even compiling the first object.
Not all people unconditionally
i stand corrected about -mno-cygwin, it does seem great and i can
understand why one would want not letting go of it.
it's hard to find info about it on cygwin.com, but searching through
their mailing list archives, there are tons of messages evocating it.
some dating from year 2000 were
On 27/11/10 6:32, dkauf...@rahul.net via RT wrote:
The last proposed change would break the build for mingw done under
cygwin, since the -mno-cygwin flag is critical there. The only place
I see where OPENSSL_SYSNAME_WIN32 is used is to define MS_STATIC.
MS_STATIC is used in 20 places in the
[houz...@gmail.com - Sat Nov 27 15:28:10 2010]:
so a follow-up problem here may be to actually check these uses of
MS_STATIC and see if they are safe - my guess is that they have been
forgotten and they are not sane to use anymore.
The ones in crypto/evp don't make sense any more. They
On Sat, 27 Nov 2010, Zouzou via RT wrote:
On 27/11/10 6:32, dkauf...@rahul.net via RT wrote:
The configure settings for mingw were clearly written with compiling
from cygwin in mind. Perhaps the cygwin build and the MSYS builds are
now different enough, that what you may really be asking
On 27/11/10 6:32, dkauf...@rahul.net via RT wrote:
The last proposed change would break the build for mingw done under
cygwin, since the -mno-cygwin flag is critical there. The only place
I see where OPENSSL_SYSNAME_WIN32 is used is to define MS_STATIC.
MS_STATIC is used in 20 places in the
hello,
i am reporting a bug with regards to a missing flag in MinGW targets.
the bug is present in both 0.9 and 1.0 branches; it is (in our case)
only leading to crashes in 1.0.
the missing flag is: OPENSSL_SYSNAME_WIN32
it is always defined for MSVC targets, but MinGW ones are forgetting to
On Fri, 26 Nov 2010, Zouzou via RT wrote:
i am reporting a bug with regards to a missing flag in MinGW targets.
the bug is present in both 0.9 and 1.0 branches; it is (in our case)
only leading to crashes in 1.0.
the missing flag is: OPENSSL_SYSNAME_WIN32
it is always defined for MSVC
On Fri, 26 Nov 2010, Zouzou via RT wrote:
i am reporting a bug with regards to a missing flag in MinGW targets.
the bug is present in both 0.9 and 1.0 branches; it is (in our case)
only leading to crashes in 1.0.
the missing flag is: OPENSSL_SYSNAME_WIN32
it is always defined for MSVC
12 matches
Mail list logo
