On Tue, Nov 03, 1998, Jan Wedekind wrote:
> 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 :-)
Great.
>[...]
> 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)
At least under FreeBSD with gcc or egcs it's not needed. But I'll add a
similar patch to libssl.module for 2.1b8. I just want to make it more
portable by replacing dirname with sed and the if-clause with a case-clause
which checks for more variants like gcc|*/gcc|etc. Thanks for testing the DSO
support and for your feedback, Jan.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
