So I have to reimplement the code found in crypto\threads\th-lock.c?
Is there a problem with those codes?
Why aren't they compiled in the library by default?

Fr�d�ric Giudicelli
http://www.newpki.org

----- Original Message ----- 
From: "Richard Levitte - VMS Whacker" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, December 27, 2003 2:08 AM
Subject: Re: CRYPTO_thread_setup/CRYPTO_thread_cleanup declaration?


In message <[EMAIL PROTECTED]> on Sat, 27 Dec 2003
01:23:25 +0100, Fr�d�ric Giudicelli <[EMAIL PROTECTED]> said:

groups> I cant' find where "CRYPTO_thread_setup" and
groups> "CRYPTO_thread_cleanup" are declared.

You need to use CRYPTO_set_locking_callback(),
CRYPTO_set_dynlock_create_callback(),
CRYPTO_set_dynlock_lock_callback(), and
CRYPTO_set_dynlock_destroy_callback(), to set up all the proper
callbacks.  They are declared in openssl/crypto.h

-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.
You don't have to be rich, a $10 donation is appreciated!

-- 
Richard Levitte   \ Tunnlandsv�gen 3  \ [EMAIL PROTECTED]
[EMAIL PROTECTED]  \ S-168 36  BROMMA  \ T: +46-8-26 52 47
                    \      SWEDEN       \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to