I'm slightly confused as to how/where the CPPFLAGS is reset or changed at all in filter/config.m4.

The only difference I can see is that there's an extra PHP_ADD_EXTENSION_DEP?

Is this just a question of adding the PHP_ADD_EXTENSION_DEP?

Since I don't have a build box without pcre on it, I'm a little lost on how to test this out.

I'm able to reproduce this on OS X by referencing the pcre installation in /opt/local.  However the filter extension does not compile correctly either.  I believe this is a problem with how the php_pcre.h is abstracted, as it expects an extension to be able to include the pcre.h file without PHP providing it's location.  There seems to be two solutions: 1) add a with-pcre-dir option to APC to include the proper path, the user will have to specify this 2) fix the PHP code to handle this properly by either abstracting it so that pcre.h does not need to be included or making the include path available to extensions.  Any other thoughts on how to go about fix this?  If, like Gopal, I'm also missing something going on in the filter or you're able to compile it please send us specifics on your configuration options etc.

Brian, I think the best way would be to do it in PHP itself instead of doing it per extension so we don't end up with many of the same configuration arguments for different extensions.

But for BC I guess we need to add a new configuration argument.

*subscribe*

RFC: http://news.php.net/php.internals/45722

A cleaner solution would be to add a macro in PHP to set the PCRE flags automatically, like what we have for openssl or libxml. PCRE detection can be tricky so such macros could be used by any extension.

While not a solution, by soft-linking to the alternate pcre.h location (e.g., "ln -s /opt/local/include/pcre.h /usr/include/php/ext/pcre/"), I was able to get it to compile.

This is so unusual that you should not mess the rest of the build system to "fix" this. And if you need external pcre, you're on your own anyway ;)

Doesn't sound like the build system changes would be so significant to cause other problems does it?  Besides, if we offer an alternative pcre DIR option during PHP configuration then we should support it actually compiling correctly, otherwise we should do-away with the configuration option all-together.  Having something that half-works doesn't seem ideal, regardless of it's frequency.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.