On Tuesday 24 December 2002 04:51, Moriyoshi Koizumi wrote: > "Edin Kadribasic" <[EMAIL PROTECTED]> wrote: > > > 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 > > I've checked your test build, and it works fine as for Apache-1.3.27. > But it still fails with Apache2... this seems another apache2filter > problem. > > Anyway this solution sounds like a quickest and most reasonable way.
Any objections to making zlib built-in extension on windows? Edin -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
