[stunnel-users] WCE 3.0 run-time error, how to work around it?

[Pierre]

Hi Robert,

We are currently working. with Mike on next 500 wce port. there are some files and scripts modified for various targets x86, armv4...

i have compiled a working version but having a run timebug "commandbar-insermenubar error 120 only works in w32 mode"...and nothing displayed in log window...well it s on progress.

maybe your pb comes from the fact that v500 expects openssl 101c and 434 was built, by me (see my web page) with my openssl v100a port...

what is your target cpu ?
are you using sdk 4.2?
tested on wm6 emulator ?
are you using my mywcemake armv4 command line tool?

let us exchange some experience, but please be patient if you want to get my new wce openssl 101c or above and stunnel.5

Regards,
Pierre

Le 12 déc. 2012 à 18:19, "Bao, Robert" <rbao at tycoint.com> a écrit :

> Mike,
>  
> The stunnel version used in our current product is 4.34. It worked well under Windows CE 3.0 and 5.0.
>  
> However I got run-time error for 5.00 beta version under WCE 3.0 (even though I disabled IPv6, took out winsock2.h/ws2tcpip.h, included winsock.h, defined “struct addrinfo”, etc ).
>  
> The error is: Error detected on SSL (read) file descriptor: Bad protocol option (WSAENOPROTOOPT) (10042)
>  
> What else I need to do to resolve or work around it?
>  
> Thank you.
>  
> Robert Bao
> Software House
> Tyco International
>  
> _______________________________________________
> stunnel-users mailing list
> stunnel-users at stunnel.org
> https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stunnel.org/pipermail/stunnel-users/attachments/20121212/0fbbf268/attachment.html>