From: Albert Chin-A-Young <[EMAIL PROTECTED]>

china> Now, OpenSSL's shared library build procedure assumes the host
china> linker has an option to suck all of the objects in an archive
china> library into the shared library.

Actually, nothing of the sort is assumed.  What *is* assumed is that
for any platform where we've included support for shared libraries,
there's a target in Makefile.org that describes how to create them.
What exactly that target does is completely up to the implementor.

china> And, if such an option does not exist, what is the solution?

To extract all the files in libcrypto.a into a temporary directory and
ld -b them into a shared library.  The same goes for libssl.a.  I
personally prefer not to use that kind of solution, but there's that
if nothing else helps.

-- 
Richard Levitte   \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken   \ S-168 35  BROMMA  \ T: +46-8-26 52 47
Redakteur@Stacken   \      SWEDEN       \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/

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]

Reply via email to