<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi again Michal,<br>
I just checked v500b3 code...<br>
<br>
Well, I think there is some misunderstanding about winsock1 and
winsock2 :<br>
<br>
at least the purpose is to have consistant use of winsock1 H files
AND lib, OR winsock2 H files AND lib.<br>
<br>
Secondly, the purpose is to make use of wsock2 when and WHERE it
REALLY exist (ie is available).<br>
<br>
To make it more clear : winsock2 and getaddrinfo ARE AVAILABLE and
working on WCE : the V434 code was assuming that getaddrinfo was
NOT existing in WCE, which is just wrong.<br>
And then, in V434, the code for common.h was containing this :<br>
<br>
#ifdef _WIN32_WCE<br>
#include <winsock.h><br>
#else<br>
#include <winsock2.h><br>
#include <ws2tcpip.h><br>
#endif<br>
<br>
meaning : use of wsock1 in WCE.<br>
THAT was leading to compilation warnng about various #define that
need -strangely- redef in winsock2, but are available in winsock1
(still following me ?...).<br>
<br>
Example : this is required in common.h if using wsock2, but NOT if
using wsock1. My 2010/11 code was fixing all this stuff.<br>
#define ENOTSOCK WSAENOTSOCK<br>
<br>
<br>
====<br>
<br>
BUT today :<br>
<br>
v500b3 common.h is JUST containing this :<br>
#ifdef USE_WIN32<br>
#include <winsock2.h><br>
#include <ws2tcpip.h><br>
<br>
well ok...nice...even for WCE...BUT inconsistent with EVC.MAK
calling winsock1 LIB !!!!!!<br>
and inconsistent with many #defines that are in fact REDEF of
existing symbols that lead to compilation warnings.<br>
<br>
So, I can help to make it more consistent :<br>
use of winsock.h if using winsock.lib (ie winsock 1 !),<br>
OR use of winsock2.h and ws2_lib (ie winsock2 !),<br>
<br>
but not mixing winsock2.h and winsock1 lib !<br>
<br>
===<br>
Something else : in log.c, many, I should say "ALL", winsock X
error codes are HARDCODED in s_strerror() : not so good for
maintainability...and stability of behavior (if codes are changing
in the lib...).<br>
<br>
I can help...but would you trust me ? :-)...<br>
<br>
I will dive in this, this week-end,<br>
<br>
See you soon,<br>
Pierre<br>
<br>
<br>
Le 06/12/2012 22:08, Michal Trojnara a écrit :<br>
</div>
<blockquote cite="mid:50C10943.3010600@mirt.net" type="cite">
<pre wrap="">On 2012-12-06 21:30, Pierre DELAAGE wrote:
</pre>
<blockquote type="cite">
<pre wrap="">My sole purpose was to replace winsock1 lib an h files with those of
winsock2 (see my modified common.h I sent you in 2010/11),
as winsock2 is available on many windows version, including 2000.
</pre>
</blockquote>
<pre wrap="">
I agree with the basic idea of using Winsock2 only.
I'd like to retain compatibility with vanilla W2K and Wship6.dll.
I hope these goals are not mutually exclusive.
About patches: Would you be so kind to send small patches for each
separate change? I really need to be able to discuss them, and decide
whether to accept or reject each of them. I refuse to apply changes I
don't understand, so you not only need to be right, but you also need to
convince me that you are. 8-)
Thank you very much for your offer to test and fix WCE.
Please take a look at the latest beta version:
<a class="moz-txt-link-freetext" href="https://www.stunnel.org/downloads.html">https://www.stunnel.org/downloads.html</a>
to help me improve quality of the final stunnel 5.00 release.
Mike
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
stunnel-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:stunnel-users@stunnel.org">stunnel-users@stunnel.org</a>
<a class="moz-txt-link-freetext" href="https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users">https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users</a>
</pre>
</blockquote>
<br>
</body>
</html>