On Fri, Nov 05, 1999, Bart N. Locanthi wrote:
> > > i get many warnings to the effect that "mod_X uses plain apache DSO and
> > > may *crash* under EAPI".
> >
> > I never tried mod_jserv, so I don't know details about it. But the warnings
> > really means that mod_jserv wasn't compiled with -DEAPI or it has an unclean
> > module structure source (where the standard Apache macros are not used).
> > Additionally, you say you get "many" warnings. For which modules do you get
> > the warnings of which one not?
>
> these all get warnings. it pretty much looks like the list of what you
> get when you say --enable-module=most. -DEAPI does appear in the
> compiles for each of them.
> [...]
> libexec/mod_unique_id.so
> libexec/mod_setenvif.so
> /usr/local/apache/libexec/mod_jserv.so
Then something is totally messed up for you. Looks like EAPI wasn't applied
correctly to your Apache source tree. I think you should start from scratch
with a fresh Apache source tree.
> > Look inside mod_jserv.c or where mod_jserv has
> > its "module" structure definition. There has to be a STANDARD_MODULE_STUFF
> > macro call.
>
> it does have that, eg
>
> module MODULE_VAR_EXPORT jserv_module = {
> STANDARD_MODULE_STUFF,
> jserv_init, /* module initializer */
> ...
>
> but i haven't found a way of passing -DEAPI to the module compile.
If mod_jserv is compiled inside the Apache source tree, it should
automatically be compiled with -DEAPI. If compiled outside with APXS just add
-DEAPI to the apxs command line.
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]
