Edin Kadribasic wrote:
You have uncovered an error in win32 configure script which is fixed now. The
next snap should again have memory limit disabled.
This is good, thank you.
One more question for my understanding:
Checking the memory limit and setting it, are 2 different things to me.
Why did
On Wednesday 07 July 2004 14:21, Peter Rendl wrote:
> Edin Kadribasic wrote:
> > Memory limit checking is not compiled in on Windows. So bugs must be
>
> caused by
>
> > something else.
>
> Unfortunately phpinfo() does not show compile options for this build.
> But http://snaps.php.net/win32/snap
Peter Rendl wrote:
Edin Kadribasic wrote:
> Memory limit checking is not compiled in on Windows. So bugs must be
caused by
> something else.
Unfortunately phpinfo() does not show compile options for this build.
But http://snaps.php.net/win32/snapshot.log contains this line
"snapshot: forcing me
Edin Kadribasic wrote:
> Memory limit checking is not compiled in on Windows. So bugs must be
caused by
> something else.
Unfortunately phpinfo() does not show compile options for this build.
But http://snaps.php.net/win32/snapshot.log contains this line
"snapshot: forcing memory-limit on". Is it
Memory limit checking is not compiled in on Windows. So bugs must be caused by
something else.
Edin
On Wednesday 07 July 2004 12:24, Peter Rendl wrote:
> Hello all,
>
> I just fetched the latest php5 package for win32 from snaps.php.net
> (Built On: Jul 07, 2004 06:30 GMT).
>
> It seems like th