On Sat, Aug 30, 2008 at 5:16 PM, Steph Fox <[EMAIL PROTECTED]> wrote:
>>> Is there a reason phar is built shared in win32 snapshots even though
>>> the default in config.w32 is to build it statically?
>>
>> The default config.w32 (besides being wrong) is shared.
>
> ARG_ENABLE("phar", "disable phar support", "yes");
>
> I'm still not in a position to test> I do know, though, > that it all worked fine before the build system was 'upgraded' and several > of the other config.w32 files across the core were 'fixed' to accommodate > those changes. Let forget this attempt to yet again discredit the fantastic work being done by the windows team and let us try to figure out what's wrong. The behavior has changed after your dependency patch, the 3rd argument of EXTENSION has to be set to false if the extension has to be built statically. >> Why should it be built statically? > > Because that's what it says in the config file. What's the actual reason to build phar statically? -- Pierre http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
