On Thu, 28 Sep 2000, Michael J Schout wrote:
> On Wed, 16 Aug 2000, Matt Sergeant wrote:
>
> > On Tue, 15 Aug 2000, Mark D. Anderson wrote:
> >
> > > The problem was the symbol conflict between XML::Parser and apache when
> > > built with expat. This has been apparently known for over a year, but has
> > > still not been fixed last i checked, presumably because it involves 4
> > > different products interacting: apache builds with expat, modperl gets
> > > linked in, then modperl pulls in XML::Parser which pulls in expat again.
>
> [snip]
>
> > name!!! Anyway, this is a much larger problem than you expect. Not only is
> > XML::Parser pulling in a custom non-dso expat, but so is PHP, and so is
> > Sablotron (XSLT processor), and so is some TCL module... We need a single
> > DSO expat that is used by everyone, but I don't have the time or resources
> > to fix it... :-(
>
> This problem has just bitten us as well. We were building apache with expat,
> and then loading XML::Parser 2.29 in. Things became unstable very quickly. As
> a quick fix, we just disabled EXPAT from our apache builds.
>
> So I guess there is no hope of running any combination of mod_dav, XML::Parser,
> PHP, Sablotron at the same time at this point? Bummer :).
>
> I suppose the issue is that expat needs to be maintained and someone needs to
> incorporate all of hte separate patches (e.g. XML::Parser patches expat, I
> assume PHP/Sablotron etc are doing the same) into a single expat and create a
> shared library? I may be able to devote some time to this, depending on how
> much merging is involved. I will try to take a look at it over the next few
> days.
No don't - its being done now. Clark Cooper is running the project over on
source forge. However I know that Clark can be quite slow at times, so
maybe he could do with some help.
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org
