[bug-notifications] [php5 0004520]: mbregex missing from PHP

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4520 
====================================================================== 
Reported By:                opk
Assigned To:                bwalton
====================================================================== 
Project:                    php5
Issue ID:                   4520
Category:                   packaging
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2010-08-13 16:38 CEST
Last Modified:              2011-06-29 04:09 CEST
====================================================================== 
Summary:                    mbregex missing from PHP
Description: 
I'm attempting to migrate an application from blastwave stable to recent
opencsw and I get the following message:
PHP Fatal error:  Call to undefined function mb_ereg_replace

This can be reproduced easily with:
echo '<?php print mb_ereg_replace("a", "b", "lalala\n"); ?>' |
/opt/csw/php5/bin/php

According to phpinfo(), php5 was compiled with --enable-mbregex=shared yet
I can't find any shared library corresponding to mbregex. Has it perhaps
been forgotten in the packaging. I do have mbstring and it is enabled in
the configuration file. On the old installation, phpinfo() reports a bare
--enable-mbregex.
====================================================================== 

---------------------------------------------------------------------- 
 (0009157) bwalton (developer) - 2011-06-29 04:09
 https://www.opencsw.org/mantis/view.php?id=4520#c9157 
---------------------------------------------------------------------- 
The most recent test packages still exhibit this problem.  mbstring is
enabled and it seems mbregex is on by default.  I'm still investigating but
I likely won't have a fix before the pending release.