Hello again and thank you for your replies
Mark wrote:
I would recommend you always watch the warnings. Some C compilers
downgrade fairly major problems to "Warnings".
I'd recommend the same thing to myself actually. These warnings are
generated by the code in th-lock.c (compiling under Win32), which as I
understand it contains code defining the callbacks required for (a few
platform specific) threads support:
../th-lock.h: In function `CRYPTO_thread_setup':
../th-lock.h:122: warning: passing arg 1 of
`CRYPTO_set_locking_callback' from incompatible pointer type
../th-lock.h:124: warning: `return' with a value, in function returning void
../th-lock.h: At top level:
../th-lock.h:128: warning: static declaration of 'CRYPTO_thread_cleanup'
follows non-static declaration
../th-lock.h:89: warning: previous declaration of
'CRYPTO_thread_cleanup' was here
I'm not really familiar with handling void* pointers so I'm not sure how
alarming these should be.
Usman Riaz wrote:
As to your second question, I am doing the IO on BIO atomically, dont
know if its really required, :), But since my server's performance is
quite resonable with it, so it's OK with me.
Regards,
Usman.
I'll probably do it that way too. My threads are defined in another
language and I'm pretty sure there is no way for my C module to be aware
of which user thread it is currently running in... so I have nothing
relevant to call CRYPTO_set_id_callback with.
So this really isn't much of a problem for me, but I'm still curious
about the macros:
OPENSSL_THREAD_DEFINES
THREADS
OPENSSL_THREADS
Is the note in http://www.openssl.org/docs/crypto/threads.html still
valid in 0.9.8a ?
Thanks again for your answers,
--
Alain Damiral,
Université Catholique de Louvain - student
alain.damiral'at'student.info.ucl.ac.be
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
