Preston Brown wrote:> With apache 1.3.x, it is possible to compile 3rd party modules without
> having anything other than the apache header files available. We will
> make it possible to compile 3rd party modules for Secure Web Server. You
> can do this already, with the apache 1.2.6 header files we shipped in 1.0.
> However, because you have to make modules "think" they are
compiling with
> 1.3.x (which was the first official release to include DSO support) things
> can be a little bit more complex than they could otherwise be. It will be
> easier in 2.0.
>
> If you are having specific problems compiling a 3rd party module for 1.0,
> let''s discuss it on the list here, and perhaps I can help.
Do all modules currently work as DSOs? I ask because I''ve been unable
to
successfully compile mod_auth_pgsql for 1.2.6 as a DSO. When I tried to
load the mod_auth_pgsql.so I compiled, it wasn''t able to resolve symbol
module_info. When I examined the source code for mod_auth_pgsql, the
module_info struct was called something else (pgsql_auth_module)
instead. When I tried renaming the struct and recompiling, apache ceased
complaining, but started failing silently instead.
I concluded that mod_auth_pgsql really needed to be statically linked.
It sounds like version 2.0 won''t support statically-linked modules
either, and so mod_auth_pgsql won''t work with it.
--
Tod Hagan On assignment at:
Bondcliff Internet Group NetWave, Inc.
tod@bondcliff.com todh@netwavelink.com