> On 21.01.2008 14:06, Lucas Nealan wrote: >> I found out the hard way that phpize won't build some extensions like >> ext/openssl because they have no config.m4, only a config0.m4. I could not >> find a reason why this shouldn't work and propose the patch below for phpize >> to support config0.m4 as well as config9.m4. > You can just create config.m4 file with the only line: > sinclude(config9.m4)
There is only one extension with config9.m4, the recode extension and it appears to be using this expressly outside of the context of phpize however it is not problematic to include this. The other four extensions only have a config0.m4. Do we prefer to create 4 new config.m4's and sinclude the config0.m4 from there? >> With this patch the following standard extensions can now be build via >> phpize which couldn't before: >> ext/libxml >> ext/openssl >> ext/pcre >> ext/zlib > These extensions generally should not be built dynamically. I haven't seen any mention of this before in the extension documentation or README's. Can you give some insight as to why this would be the case with these extensions alone? -lucas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
