On Wed, 1 Mar 2000, Ralf S. Engelschall wrote:
*snip*
>
> The ctx is part of the EAPI patches. So if the compiler complains it
> doesn't exists as a member of the server_rec structure, this means EAPI
> was not successfully applied to your Apache source tree. Try again from
> scratch, it seems you've messed up something.
I've tried from scratch both manually and with a RPM spec file that built
fine all the way up to 2.5.0, but fails on 2.6.0 and 2.6.1..
> Believe me: mod_ssl always compiles fine against the corresponding
> Apache version, because mod_ssl sources and patches are directly
> generated via CVS from a source tree where mod_ssl lives within an
> Apache source tree. So if such errors occur this _could_ be my fault in
> releasing buggy software, but in 99.9% of the time it means the end user
> just has not applied mod_ssl correctly to the Apache source tree. The
> only compile time errors I expect are problems related to vendor header
> conflicts or problems on non-Unix platforms. But such direct compile
> errors should never occur.
Yeah, I know, this error really surprised me. I did some more
troubleshooting.. it turns out that the problem only occurs with an
--enable-rule=SSL_EXPERIMENTAL on the configure.. if I remove that flag,
everything works great. Any ideas?
--
Nate Carlson <[EMAIL PROTECTED]> | Phone : (612)943-8700
http://www.real-time.com | Fax : (612)943-8500
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
