On Fri, Sep 18, 1998, Khimenko Victor wrote:
>[...]
> > And for them you have to link the mod_proxy and mod_log_config DSOs against
> > the SSLeay libs.
>
> Oops. Why ?
Because they use SSLeay symbols: mod_log_config for the addtional
log format directives and mod_proxy in order to provide HTTPS.
> And how this was done ? I'm pretty sure then I'm took compilation
> script for 2.0.6 and made only one change for 2.0.9: ONLY name of source
> archive with patch was changed! Is 2.0.9 already link mod_proxy and
> mod_log_config against the SSLeay for me ?
I repeat: You're on a lucky system: ELF & SSLeay is a DSO. Here the DSOs have
not be explicitly linked against SSLeay because it's already available under
runtime to them. On other systems this is not the case. So, that it worked
for you is one the result of your lucky situation....
> > This works only on some platforms and only with the SHARED_CHAIN feature
> > under Apache 1.3.2.
>
> This was with plain old 1.3.1 ! What is SHARED_CHAIN, by the way ? And why it's
> needed at all ?
SHARED_CHAIN is a rule in Apache 1.3.2 (available the next days) which
automatically links DSOs against possible libs from $LIBS. This way when you
use LIBS="-lx" and libx.so exists DSOs are linked against this library, too.
It's needed to provide the symbols of libx.so to the DSO. And this is needed
on some platforms to make the DSO workable at all. Please read the
htdocs/manual/dso.html document of Apache carefully, there are those things
explained in more detail, too.
>I'm have mod_php3.so, for example, linked with GD, FreeType,
> PostgreSQL & MySQL shared libraries (while main httpd binary is NOT linked with
> any of them). All works like a charm ! What problem could be solved with
> SHARED_CHAIN if all works without SHARED_CHAIN after all ?
Wait, PHP3 is different! It's compiled either outside Apache or uses it's own
Makefile which already links against the stuff. And I say it again: That it
all worked for you without SHARED_CHAIN is only because you use a powerful
enough DSO/object-file-format system.
> > That why I support this for the experts. But for the avery user it's best to
> > link these two modules statically to avoid the common problem: "Symbol not
> > found" when loading the DSOs of mod_proxy and mod_log_config.
>
> Ok. I am right that the only possible problem with mod_proxy as DSO is
> "Symbol not found" ?
Yes.
> And that mod_proxy will work as desired this way if
> loaded without such messages ? Or there are could be some hidden problems ?
No, usually when it loads fine it should run fine, too. There are special DSO
things on some platforms (lazy loading, etc.), but these are not uses by
Apache. So when the module loads fine, it usually works fine, too.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
