At 09:56 AM 8/30/2003 -0400, Rob Richards wrote:
From: Andi Gutmans
> Ouch. Now the question is how do we solve this? Do we make ./configure
bail
> out on such versions or do we hack something into PHP so that it doesn't
> call this function more than once?
> I really want to reduce the block size in my mem manager from 256KB to
16KB
> but I can't do it right now because it kills PHP quicker (it will die in
> any case but it will take longer).

Do you know what happens if another apache mod were to be using libxml
(there are some)? Would they be sharing the same space as in, if the other
mod were to change libxml globals, would that affect the libxml globals
within the php scope? I believe they would clash but dont know for sure.

They probably would.


If so, then libxml 2.5.8 would have to be marked bad unless you can also
know when the other mods call their cleanup. This is a 2.5.8 issue only as
it was introduce in that version and fixed in 2.5.9.

Can someone who knows configure well please add a check and bail out on 2.5.8?


Thanks,

Andi

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



Reply via email to