On 21/06/02, "Brian France" <[EMAIL PROTECTED]> wrote: > My goal is NOT TO REMOVE mbstring FROM THE ext DIRECTORY. Here is > what I do want:
I understood that. > I guess my sales pitch of "can be removed from ext" back fired. :-) > Should of just stuck with "can be built as a shared extension". What I said is still valid: > >If you do decouple mbstring, please make sure that the mbstring headers > >are still installed in the pear include directory too! If mbstring is built as a shared extension, you need to ensure that it's headers are also installed in the pear header directory, otherwise configuring other modules that depend upon it will fail. --Wez. -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
