Re: [DIFF] phpize won't work on extensions without config.m4

On 22.01.2008 01:07, Lucas Nealan wrote: > 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? Well, technically it should not matter whether it's config9 or config0. But there is a reason why those extensions use config0 - other extension should know if they are enabled or not, i.e. their configure checks must be run first. So I believe you're going to have problems if you build them dynamically. >> 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? These extensions provide common functionality and other extensions rely on their configure checks. OpenSSL, PCRE, libxml and Zlib checks are done first (because of config*0*.m4), so that other extensions might use their defines and variables without implementing the same configure checks over and over again. There are also extensions using config*9*.m4, their configure checks are run last. -- Wbr, Antony Dovgal