You're right.. libcrypto/ssl.a should get linked with mod_ssl.so rather than httpd. I did try it out initially - with a small hack into the ssl makefile, but then gave up - as it involved modifying the autoconf script(something which i don't know).
Thx -Madhu -----Original Message----- From: Doug MacEachern [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 03, 2001 8:47 AM To: [EMAIL PROTECTED] Subject: Re: --enable-ssl=shared On Wed, 3 Oct 2001, Aaron Bannert wrote: > So you're saying that libssl.so and libcrypto.so aren't showing up > when you run ldd on either httpd or mod_ssl.so? Just for reference, > what is ldd giving you for httpd and mod_ssl.so? (You may not want to > copy it here, but ldd -v is interesting too). no, mine is linked against lib{crypto,ssl}.a there are no .so's in /usr/local/ssl/lib i'm just noticing now for the first time lib{crypto,ssl}.so in /usr/lib but if mod_ssl is built shared, -lssl -lcrypto should get linked against mod_ssl.so rather than httpd, right? % ldd bin/httpd libaprutil.so.0 => /home/dougm/ap/prefork/lib/libaprutil.so.0 (0x40017000) libapr.so.0 => /home/dougm/ap/prefork/lib/libapr.so.0 (0x40028000) libm.so.6 => /lib/libm.so.6 (0x40052000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x40071000) libnsl.so.1 => /lib/libnsl.so.1 (0x400a0000) libdl.so.2 => /lib/libdl.so.2 (0x400b7000) libexpat.so.0 => /home/dougm/ap/prefork/lib/libexpat.so.0 (0x400ba000) libpthread.so.0 => /lib/libpthread.so.0 (0x400e1000) libc.so.6 => /lib/libc.so.6 (0x400f7000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) % ldd modules/mod_ssl.so libc.so.6 => /lib/libc.so.6 (0x40032000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
