>Ah, I should have been clearer on this: I suggested CVS/8th
>specifically to undo the change that brought midgard-config, to rule out
>that they were causing the segfault. So try again from your new
>situation using the latest CVS.
Doing this now...
>> Again, what i did is get the CVS from july8th, and copied these cvs
>> files to the unpacked lib/mod/php4 directories (regular download) so that
>> the orig files would be replaced by the cvs ones. ( I hope this last
>> sentence makes sense...i don't know of another way of explaining...and i
>> really hope that is ok to do!)
>Hmmmm... that's very non-standard procedure. My recommendation is to use
>fetchcvs to grab the latest, use bootstrap to prepare for compilation,
>and work from the directories fetchcvs downloaded. Even if the above
>procedure seems to work.
i think i did this a couple of times before, but i'll do it this
way....hopefully a different error will occur!:)
>What does 'midgard-config --report' return?
midgard-config didn't exist in this cvs. ( from before july 8)
>midgard-config --includes is supposed to provide the place to look for
>expat.h. If it doesn't, I must fix midgard-config.
I don't think you should worry about that because i don't think the cvs from
before july 8 had a midgard-config.
>How was PHP4 compiled, BTW?
umm...geez...sooo long ago...what do you mean how was it compiled? From
source...with dso support..
Aditya
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
