> A few collegues and I found that to be quite dangerous. Suppose
> someone wants to use OpenSSL as part of another shared library.
> You'll end up with a shared library where parts are relocatable and
> parts are not. That's extremely bad.
But that's allways what happens if you link an archive library
into a shared library.
If I build an archive library it's probably because I don't
want the slow-down of PIC code.
"Doctor, doctor, it hurts when I do this"
"Well, don't do that then".
--
John Hughes <[EMAIL PROTECTED]>,
CalvaEDI SA. Tel: +33-1-4313-3131
66 rue du Moulin de la Pointe, Fax: +33-1-4313-3139
75013 PARIS.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
