> > 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_vhost_alias.so
libexec/mod_env.so
libexec/mod_mime_magic.so
libexec/mod_mime.so
libexec/mod_negotiation.so
libexec/mod_info.so
libexec/mod_include.so
libexec/mod_autoindex.so
libexec/mod_dir.so
libexec/mod_cgi.so
libexec/mod_asis.so
libexec/mod_imap.so
libexec/mod_actions.so
libexec/mod_speling.so
libexec/mod_userdir.so
libexec/mod_alias.so
libexec/mod_access.so
libexec/mod_auth.so
libexec/mod_auth_anon.so
libexec/mod_auth_dbm.so
libexec/mod_digest.so
libexec/mod_cern_meta.so
libexec/mod_expires.so
libexec/mod_headers.so
libexec/mod_usertrack.so
libexec/mod_unique_id.so
libexec/mod_setenvif.so
/usr/local/apache/libexec/mod_jserv.so
> 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.
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
