On Tue, 15 Aug 2000, Mark D. Anderson wrote:
> (not sure whose email got delayed since i posted this question some time ago --
> thanks for the tip though on how to get more meaningful modperl crash info).
>
> 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.
>
> I rebuilt apache disabling expat and all was fine.
>
> This is so common a configuration (apache, modperl, and XML::Parser), i have
> to assume that the only reason there is not rioting in the streets is because
> perhaps it only happens the way i built it (apache statically linking modperl).
I'm rioting, I'm rioting... But I don't have quite enough time to devote
to it... And I wanted to register the domain name 4expat.org to try and
sort this out but my ISP wants £100 a year to do dns on an extra domain
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... :-(
--
<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
