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 already talking about its deprecation. it looks like the flag got removed during the GCC 3 -> GCC 4 switch. GCC 3 used to be the default for a while on Cygwin, now it is GCC 4. as a matter of fact, i can still use GCC 3 and -mno-cygwin on recent Cygwin installations: $ gcc-3 -mno-cygwin gcc-3: no input files $ gcc -mno-cygwin gcc: The -mno-cygwin flag has been removed; use a mingw-targeted cross-compiler. Doug's solution (new target in Configure) sounded fine by me but Andy's (decide based on the compiler whether -mno-cygwin can be added or not) seems even better. i'm not sure how this will be done but if greping through "gcc --target-help" is too complicated, one could also just look at the compiler major version (3 or 4) or try to run "gcc -mno-cygwin" and see if it errors out. Stephen has removed the offending MS_STATIC declarations so defining OPENSSL_SYSNAME_WIN32 may not even be needed now for MinGW targets. the only remaining uses i can see are debug / test related or not critical (eg rand file generation). Zouzou ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
