In message <[EMAIL PROTECTED]> on Mon, 16 Dec 2002 21:30:46 +0100, Andy
Polyakov <[EMAIL PROTECTED]> said:
appro> > Just take the lib*.a and relink it
appro> > explicitly:
appro> > mkdir tmp; cd tmp; ar x ../libcrypto.a; ld -r -o ../libcrypto.o *.o
appro> > ld -G -o libcrypto.so libcrypto.o -l<whatever>
appro>
appro> As mentioned calling /usr/ccs/bin/ld *is* an alternative. Or is it?
appro> Imagine following scenario. You compile the toolkit with gcc and link
appro> with ld as you suggest. This might leave unresolved references to
appro> libgcc. Now if it did, then attempt to cc ... -lssl would fail... A.
OK, I lied a message ago. In 0.9.8-dev's Makefile.shared, the first
ld is actually an ld, while the second shown above is done through cc
or gcc.
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 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]
