> On Thursday 26 December 2002 21:14, Frank M. Kromann wrote:
>
> > I think this is a good idea too, but on my system zlib.dll is required
to
> > run php.exe. If this is the case with the official build we might have
a
> > support issue. This could be a local problem with the way I compile
the
>
On Thursday 26 December 2002 21:14, Frank M. Kromann wrote:
> I think this is a good idea too, but on my system zlib.dll is required to
> run php.exe. If this is the case with the official build we might have a
> support issue. This could be a local problem with the way I compile the
> Zlib librar
Hi,
I think this is a good idea too, but on my system zlib.dll is required to
run php.exe. If this is the case with the official build we might have a
support issue. This could be a local problem with the way I compile the
Zlib library ?
- Frank
> On Thu, 26 Dec 2002, Edin Kadribasic wrote:
>
>
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
"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
> 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 buil
On 2002-12-23 11:09:40, Wez Furlong 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?
Probably the second one is the easier solution.
W
I have taken a short look at the code and i think Morioshi is correct.
zlib_ouput_compression doesn't seem work when zlib si compiled as a
shared module. But i will not have time for this until after x-mas.
marcus
At 09:11 23.12.2002, Moriyoshi Koizumi wrote:
As far as I've looked into this prob
As far as I've looked into this problem, absense of "Content-Encoding"
field in the response headers, apparently a side effect of the patch of
rev 1.138 for main/SAPI.c, results in un-inflated output on the clients.
Because the patch was designed only to work with statically linked zlib
module,
This needs one of you "output guys" to resolve it.
Andrei mentioned something about making the final release before 1st
Jan, so if you can, please get your coding-butts in gear :)
--Wez.
On 22 Dec 2002 [EMAIL PROTECTED] wrote:
> ID: 21139
> Updated by: [EMAIL PROTECTED]
>
10 matches
Mail list logo