Hi,
in my test environment I got it running:
apache-1.3.3, fully modularized with additional share modules:
mod_frontpage, mod_perl and or course: mod_ssl :-)
Ralf: As I mailed you (and by accident to the list) before
concerning the problems while patching the source against
1.3.3 must have been my fault;
I just tried it out with a clean source tree without probs.
I ran into the following problems on Solaris with
SunOS 5.5.1 Generic_103640-12, gcc 2.[78].x, SSLeay-0.9.0b:
SSLeay (crypto/bn/bn_word.c, line 81) needs the BigNum modulo
from libgcc (symbol __umoddi3 there within), but libgcc
of course is *not* included to the ld statement.
So we need a conditional extension to SSL_LIBS with the
mod_ssl Makefile for use with gcc, producing something like this:
LIBGCC:sh =`gcc -print-libgcc-file-name`
SSL_LIBS=-lssl -lcrypto -L`dirname $(LIBGCC)` -lgcc
or better integrate this stuff into libssl.module (module definition file):
--- libssl.module.orig Tue Nov 3 17:49:37 1998
+++ libssl.module Tue Nov 3 18:44:03 1998
@@ -356,6 +356,12 @@
echo "SSL_PROGRAM=$SSL_PROGRAM" >>$my_outfile
echo "SSL_VERSION=$SSL_VERSION" >>$my_outfile
if [ ".$my_buildtype" = .DSO ]; then
+ # check for gcc library (__umoddi3), needed for DSO ([EMAIL PROTECTED])
+ if [ ".$CC" = ".gcc" -o ".$CC" = ".egcs" ]; then
+ libgcc=`$CC -print-libgcc-file-name`
+ libpath=`dirname $libgcc`
+ SSL_LIBS="$SSL_LIBS -L$libpath -lgcc"
+ fi
echo "SSL_LIBS=$SSL_LIBS" >>$my_outfile
echo "SSL_LDFLAGS=$SSL_LDFLAGS" >>$my_outfile
else
For me that works fine, but eventually it's only needed for some
versions / combinations of SunOS and gcc ?
(anyway it should work with all of them)
Jan
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
