On Tue, 10 Oct 2000, Matt Sergeant wrote:
> On Mon, 9 Oct 2000, Herrington, Jack wrote:
>
> > This allows for XML parsing with no change to the Perl code. I'm just not
> > sure what I am losing in Apache (which is where I make the change). What
> > does losing EXPAT do to Apache?
>
> You lose mod_dav, and maybe future modules that use the built in expat
> support. But nothing serious.
All of hte problems that you are seeing are essentially due to the fact that
XML::Parser uses its own version of expat that has been patched. So the expat
code from XML::Parser conflicts with the expat code from apache if you built
with RULE_EXPAT=yes. Things get further complicated if you use php, which also
pulls in a customized version of expat, causing more conflicts.
There is work to fix this going on by maintaining expat so that it contains all
of hte patches from these projects. This is on sourceforge at
http://expat.sourceforge.net/ They have a preliminary release that I have
built as a shared library and it works fine on our system. We use it this way:
Compile apache with: RULE_EXPAT=no
Build expat from sourceforge as a shared library
fiddle with XML::Parser makefiles to cause it to link against libexpat.so
instead of bulding its customized version.
build mod_dav by linking with libexpat.so
So XML::Parser and mod_dav can co-exist happily in this situation.
I have .rpms and .src.rpm files of expat, XML::Parser, mod_dav which include
the patches. If anyone is interested, please let me know and I will be happy
to forward them to you (the rpms, or the patches).
Mike
