On Wed, Jan 20, 1999, [EMAIL PROTECTED] wrote:
> Full_Name: Ashley Brandwood
> Version: 1.2.4
> OS: Solaris 2.6
> Submission from: nnuk-ab.easynet.co.uk (195.40.56.48)
>
> has anyone been able to get mod_coldfusion (from allaire.com)
> and apache 1.3 and mod_ssl work together? As far as I can tell
> problems are caused by both SSLeay and mod_coldfusion having
> identical symbols in it ...
>
> Any suggestions as how to get around this (including the possibility
> of linking the mod_coldfusion.a into the SSLeay stuff ...
When mod_colfusion really exports conflicting symbols other than
coldfusion_module (which should not conflict) then it's programmed not very
clean, of course. At least a common prefixes should be used. But now to the
problem: Seems like the mod_coldfusion is a DSO, so symbol conflicts should
not occur, because Apache lookups only the coldfusion_module symbol in the
mod_coldfusion.so. Instead your symbol problems has to be of different
kind.
Nevertheless you've one more problem: mod_coldfusion will never work with
Apache+EAPI, because it has a different module structure (the one looked up
under coldfusion_module). This means especially it is missing NULL's at the
end of this static structure which will always leads to core dumps when
Apache's core stuff tries to dispatch over it.
So, independent of your symbol problem you need the source of mod_coldfusion
or you have no chance.
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]
