Re: #20755 [Opn->Ver]: exif relocation error

--snip > If you compile mbstring as static module, you can workaround this > error. It's not very good idea to enable it anyway.. I'm wondering why you referred to enabling mbstring as no good idea in this report. I believe the problem has been properly avoided, or am I missing something? > For the mbstring authors: You should decide whether or not to allow > external usage of these functions (ie. in other extensions) or disable > the building of this extension as shared altogether.. What decision? We actually externalise some functions just for that purpose. Perhaps did you mean integration of mbstring into core part? BTW we are now working on a new mbstring API specification so that other extension authors can use the functions with more convenience and in no more doubt about their usage. If we should treat it in a special way, please let us know. Moriyoshi