You probably link to libcrypto.so and libssl.so dynamically anyways, so there is truly no measurable difference.
And if you link static to libcrypto.a/libssl.a, you may find that you cannot load mod_ssl or other modules (e.g. mod_auth_ldap) which bind directly or indirectly to libcrypto.so/libssl.so. Bill John P. Dodge wrote:
Never saw any response to this question: Is there a consensus on compiling mod_ssl as shared or static? Thanks. ---------------------------------------- "Mon aéroglisseur est plein d'anguilles" John P. Dodge Boeing Shared Services --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] .
--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
