I'm wondering... Currently, we run ranlib on libcrypto.a from each
Makefile.ssl through the crypto/ directory tree. And then again when
installing it. Is that really necessary? On most system I'm
compiling on, ranlib on libcrypto.a takes a noticeable amount of time,
and as far as I understand, quite needlessly so. Not doing ranlib
except when installing or possibly creating shared libraries doesn't
feel much like a loss. The openssl program will not get larger, or
will it?
So, is there a real reason we ranlib all over the place? If not, does
anyone mind if I remove all those and just leave it for the
installation part?
--
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]
