I can see from the archives that the DEAPI issue is a well-beaten horse. I also see the documentation on Apache/Tomcat's site. However, I am still running into an issue with it. And, I think it might be because I don't have a "high-level-view" of what DEAPI really is.
I am getting the good'ol error of: Loaded DSO libexec/mod_jserv.so uses Plain Apache.....recompile using -DEAPI I have seen in the archives folks mentioning (including Apache/Tomcat's site) to add the directive --enable-eapi (or perhaps --enable-deapi) when using ./configure in the mod_ssl directory. When I do so, it tells me this is an illegal argument. I have seen folks say to provide the environment variable CFLAGS=-DEAPI....and then export it with export CFLAGS. With this variable set, my ./configure runs (without using the -enable-eapi directive) successfully, but still I get the Plain Apache error when launching apachectl startssl. Note that everything works...can use https, etc., but still I get this warning. So, I think I am missing the big picture. Does my mod_jserv.so need to be rebuilt somehow such that as I can add it as a directive in the compile command like --add-module=<path>/mod_jserv.c ? What I am using right now to compile is: ./configure --with-apache=../apache_1.3.12 \ --with-ssl=../openssl-0.9.6b \ --with-rsa=../rsaref-2.0/local \ --prefix=/usr/local/apache_1.3.12 \ --add-module=../apache_1.3.12/src/modules/standard/mod_so.c \ --with-crt=<path to crt>/www.mydomain.com.crt \ --with-key=<path to key>/www.mydomain.com.key Again, this is with my CFLAGS environment variable set ( CFLAGS=-DEAPI ) Should I be doing something to mention the jserv module in the ./configure ? Can anyone give a one-liner description of what DEAPI is and why this issue exists? Thanks for your help. Rob ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
