Re: [PATCH] Allow for using external liboniguruma
| From: | Lars Strojny | Date: | Sat, 17 May 2008 20:47:19 +0000 |
| Subject: | Re: [PATCH] Allow for using external liboniguruma | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-37696@lists.php.net to get a copy of this message | ||
Hi Christian,
Am Samstag, den 17.05.2008, 22:36 +0200 schrieb Christian Hoffmann:
[...]
> Relevant code from ext/mbstring/config.m4:
> 275 if test "$PHP_MBREGEX" != "no"; then
> 276 AC_MSG_ERROR([multibyte regex support must be disabled, use
> --disable-mb regex])
[...]
> So, will mbregex be re-enabled in HEAD? If yes, then I'll be happy to
> create the patch, otherwise, the whole oniguruma stuff should
> probably
> be dropped.
I would guess that it's due to general unicode support. But it would be
interesting to know, if the assumption is correct. Another sidenote:
Illia, would you like to have this patch for 5_2?
> On a different note, --disable-all seems to behave a bit strange in
> case of PCRE:
> $ ./configure --disable-all --disable-cgi --enable-cli
> checking for PCRE support... no
> configure: error: Could not find pcre.h in no
>
> This is really confusing, either it should be allowed to disable PCRE
> as it used to be in 5_2 (i.e. making "no" meaning no and not be
> interpreted as a path) or always default to "yes" if no path was
> given.
That's indeed not optimal. But if ext/mbstring is removed completely, it
won't be a problem really. Can someone clarify the plans for HEAD and
mbstring?
cu, Lars
Attachment: [application/pgp-signature] Dies ist ein digital signierter Nachrichtenteil signature.asc
Attachment: [application/pgp-signature] Dies ist ein digital signierter Nachrichtenteil signature.asc