Hello all,
I just downloaded and compiled SSLeay 0.9.0 under BeOS PPC PR2 (should work
for R3+ as well, but I haven't had a chance to try yet). It required a few
modifications, which I have collected in the form of 'diff' output (I won't
spam them to the list, but they are available if someone wants them). I'm
not worried about most of the changes, but a few make me nervous. In par-
ticular:
#define SHUTDOWN(fd) closesocket(fd)
from e_os.h and changing "i=getsockopt(sock,SOL_SOCKET,SO_ERROR,&j,&size)"
to "i=0; j=errno" in apps/s_socket.c and crypto/bio/b_sock.c. In the first,
BeOS doesn't have shutdown(), so I figured "closesocket()" was all that was
needed... For the second, BeOS does not support SO_ERROR and AFAIK does not
provide a way to check any errors on a socket; you have to check errno after
the call. In the SSLeay code BIO_sock_error() appeared to be called before
any other system functions after a read or write....but I'm not that familiar
with it.
Due to the BeOS's highly multi-threaded philosophy, I think it would be best
to include the thread setup and locking functions by default. But where
should they be added? (Currently they're in crypto/threads/th-lock.c, but
as far as I can tell that doesn't get compiled anywhere.)
Pete
p.s. I have not built it as a shared library (I'm still trying to figure
out just how to do that) but I will do that eventually; I doubt it will
require any additional source modifications.
+-------------------------------------------------------------------------+
| Administrative requests should be sent to [EMAIL PROTECTED] |
| List service provided by Open Software Associates, http://www.osa.com/ |
+-------------------------------------------------------------------------+
