On Sat, Aug 14, 1999, Ofer Inbar wrote:
> > That all works fine, and the Apache configure sees both mod_perl and
> > mod_ssl and configures them in. Then I try to run the Apache make,
> > and it gets as far as building mod_ssl and croaks with this error:
> >
> > ===> src/modules/ssl
> > gcc -c -I../../os/unix -I../../include -DSOLARIS2=260 -DMOD_PERL
>-DMOD_SSL=203111 -DEAPI `../../apaci` -DSSL_COMPAT \
> > -DSSL_USE_SDBM -I/src/openssl-0.9.4/include -DMOD_SSL_VERSION=\"2.3.11\" mod_ssl.c
> > In file included from mod_ssl.c:65:
> > mod_ssl.h:496: parse error before `AP_MM'
> > mod_ssl.h:496: warning: no semicolon at end of struct or union
> > mod_ssl.h:511: parse error before `}'
> > mod_ssl.h:511: warning: data definition has no type or storage class
> > *** Error code 1
> > make: Fatal error: Command failed for target `mod_ssl.o'
> >
> > I am not using MM (the load on this server will be very light), and
> > it's not installed on the system. It looks like mod_ssl.h was
> > expecting a "typedef void AP_MM;" but the header file for it was never
> > included. I tried running the Apache configure from the Apache
> > directory with the same options, and got the same error when I ran make.
>
> Nobody has answered so far.
>
> I wonder, has *anyone* built Apache 1.3.6 with mod_ssl 2.3.x & openssl 0.9.4
> but *without* mm, successfully? Is it at all possible to do this? How?
Errr.... I'm really confused why some of you get this error. I've
double-checked this and Apache 1.3.6 + mod_ssl 2.3.11 compiles fine with and
without MM. Seems like your Apache source tree was not correctly patched. Try
it again with a really _fresh_ Apache source tree and make sure no *.rej files
occur there after applying mod_ssl.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
