I encountered the same problem (on HPUX V10). The complaint was resolved by
adding SSL_VENDOR=yes in the Configuration file. It looked to me that the
code was relying on the definition of ctx in the SSLSrvConfigRec structure,
and that was only defined in an ifdef SSL_VENDOR. Once I did that it
compiled fine and is currently running. I sure thought that I had all the
EAPI patches on correctly (?).
Deborah Hansknecht
Sandia National Labs
505 844-6532
-----Original Message-----
From: Ralf S. Engelschall [mailto:[EMAIL PROTECTED]]
Sent: March 01, 2000 12:23 AM
To: [EMAIL PROTECTED]
Subject: Re: compile problems - 2.6.1 / 1.3.12
On Tue, Feb 29, 2000, Nate Carlson wrote:
> I'm trying to compile 2.6.[01] against 1.3.12, and the compiler is
> spitting out the following:
>
> gcc -c -I../../os/unix -I../../include -O2 -mpentium
> -fno-strength-reduce -DLINUX=2 -DMOD_SSL=206101 -DEAPI -DUSE_EXPAT
> -I../../lib/expat-lite `../../apaci` -fpic -DSHARED_MODULE -DSSL_COMPAT
> -DSSL_EXPERIMENTAL -DSSL_USE_SDBM -I/usr/include
> -DMOD_SSL_VERSION=\"2.6.1\" ssl_engine_ext.c && mv ssl_engine_ext.o
> ssl_engine_ext.lo
> ssl_engine_ext.c: In function `ssl_ext_mp_init':
> ssl_engine_ext.c:333: structure has no member named `ctx'
> ssl_engine_ext.c: In function `ssl_ext_mp_clientcert_cb':
> ssl_engine_ext.c:595: structure has no member named `ctx'
> make[4]: *** [ssl_engine_ext.lo] Error 1
> make[3]: *** [all] Error 1
> make[2]: *** [subdirs] Error 1
> make[2]: Leaving directory `/usr/src/redhat/BUILD/apache_1.3.12/src'
> make[1]: *** [build-std] Error 2
> make[1]: Leaving directory `/usr/src/redhat/BUILD/apache_1.3.12'
> make: *** [build] Error 2
>
> (this build is from a rpm spec file that worked fine for 2.5.0/1.3.11 ..
> i've also tried it manually with the same results.)
>
> Any ideas before I go digging?
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.
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.
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]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
