> Isn't the solution as "simple" as changing the #ifdef to include > COMPILE_DL_ZLIB in the checks, or is this another situation where the > zlib extension should be compiled into the distribution itself? > > Is there a problem with doing that in the win32 build Edin? > (it seems that the unix build will also have the same problems if zlib > is built as a shared extension - there was even a bug report today about > related issues).
One of the solutions for the windows build is to compile zlib module into php4ts.dll statically. In that way all the problems go away and its a nice module to have built-in anyway. I have a patch ready and a test build of php4ts.dll at http://snaps.php.net/~edink/php4ts.dll-zlib.zip Edin P.S. Make sure to remove extension=php_zlib.dll from your php.ini -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
