Hi, Dave.
If you are having difficulties with reading HTML mail, which is rather standard anyway, that would likely be an issue with your reader program. I am not seeing the problem in the least. I thought you might want to be aware of that. J John From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Dave Thompson Sent: Monday, October 22, 2012 8:17 PM To: openssl-users@openssl.org Subject: RE: RE: problem with cross compile OpenSSL First: please turn off HTML mail if possible. It's hard to read to start with, and when you start modifying purported quotes it's almost impossible. _____ From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of ??? Sent: Sunday, 21 October, 2012 20:49 To: openssl-users@openssl.org Subject: Re:RE: problem with cross compile OpenSSL Dave,thanks very much for you reply. The problem is still existing. but you also say the below. There's something in the HTML which causes Outlook to refuse to reply correctly to it, so I'm just replying out of order, even though that's bad netiquette on lists like this. That's quite weird. You may have to debug it, if you can debug (reasonably) on your target. Two more things I would try first: On checking the code I am reminded s_client uses mostly if not entirely nonblocking socket I/O. Try a plain TCP socket program with nonblocking socket and select calls. If that also works okay: Try using only the BIO level -- create and connect a socket (to a plaintext host), wrap it in BIO_new_socket(sd), set it nonblocking, and try BIO_write (and BIO_read) on that. If that gets the equivalent error you have a simpler case to debug. If not, I can't imagine what SSL level is doing that causes the BIO level to get this error; good luck. It runs well when I just does a plain TCP socket connection.
