Everything
php
Learn Community Releases The PHP Project
Home » Project » Newsgroups » php.internals » 'make install' fails when --enable-memory-limit is present »

'make install' fails when --enable-memory-limit is present

php.internals

Zeev Suraski

22 years ago
Apparently, the default 8MB are not enough for the PEAR installation, so it bails out when trying to 'make install'. Changing php.ini doesn't have any effect since the installation uses -n to ignore any php.ini's. My suggestion - add -dmemory_limit=32M to PEAR_INSTALL_FLAGS (16M solves the problem on my Linux box, but I think we should go higher to be on the safe side). Was this ever discussed? Any reason not to do it? Zeev

Derick Rethans

22 years ago
On Wed, 23 Jun 2004, Zeev Suraski wrote:
> Apparently, the default 8MB are not enough for the PEAR installation, so it > bails out when trying to 'make install'.
Those default 8MB works for me...
> My suggestion - add -dmemory_limit=32M to PEAR_INSTALL_FLAGS (16M solves > the problem on my Linux box, but I think we should go higher to be on the > safe side).
We prolly should highen the limit to a default 16M too for PHP 5. Derick

Zeev Suraski

22 years ago
At 16:21 23/06/2004, Derick Rethans wrote:
>On Wed, 23 Jun 2004, Zeev Suraski wrote: > > > Apparently, the default 8MB are not enough for the PEAR installation, so it > > bails out when trying to 'make install'. > >Those default 8MB works for me...
It does not for me. Maybe it's related to some modules I'm using, but it actually doesn't work for in neither 4.2.3 nor 4.3.7.
> > My suggestion - add -dmemory_limit=32M to PEAR_INSTALL_FLAGS (16M solves > > the problem on my Linux box, but I think we should go higher to be on the > > safe side). > >We prolly should highen the limit to a default 16M too for PHP 5.
Why? Zeev

Derick Rethans

22 years ago
On Wed, 23 Jun 2004, Zeev Suraski wrote:
> > > My suggestion - add -dmemory_limit=32M to PEAR_INSTALL_FLAGS (16M solves > > > the problem on my Linux box, but I think we should go higher to be on the > > > safe side). > > > >We prolly should highen the limit to a default 16M too for PHP 5. > > Why?
Because applications in PHP 5 will most likely be larger usually due to the better support for OO. People will earlier attempt to create more complex applications and easily get over the low limit of 8MB. Additionaly to this, you can't even resize a truecolor jpg (1600x1200) at this moment with the default memory limit because GD uses about 4 times the amount of pixels in an image as memory. regards, Derick

Gareth Ardron

22 years ago
On Sat, 2004-07-03 at 12:13, Derick Rethans wrote:
> > > > My suggestion - add -dmemory_limit=32M to PEAR_INSTALL_FLAGS (16M solves > > > > the problem on my Linux box, but I think we should go higher to be on the > > > > safe side). > > >We prolly should highen the limit to a default 16M too for PHP 5.
> Because applications in PHP 5 will most likely be larger usually due to > the better support for OO. People will earlier attempt to create more > complex applications and easily get over the low limit of 8MB. > Additionaly to this, you can't even resize a truecolor jpg (1600x1200) > at this moment with the default memory limit because GD uses about 4 > times the amount of pixels in an image as memory.
To be honest, I've never understood why. php_imlib2 seems to run though things fine with large files, and the structure of that is hardly uncommon, and it's not like I've been doing anything dodgy with fudging the zend api to get it to work right. Might take a look at that one tomorrow.

Derick Rethans

22 years ago
On Sat, 3 Jul 2004, Gareth Ardron wrote:
> On Sat, 2004-07-03 at 12:13, Derick Rethans wrote: > > > > > > My suggestion - add -dmemory_limit=32M to PEAR_INSTALL_FLAGS (16M solves > > > > > the problem on my Linux box, but I think we should go higher to be on the > > > > > safe side). > > > >We prolly should highen the limit to a default 16M too for PHP 5. > > > Because applications in PHP 5 will most likely be larger usually due to > > the better support for OO. People will earlier attempt to create more > > complex applications and easily get over the low limit of 8MB. > > Additionaly to this, you can't even resize a truecolor jpg (1600x1200) > > at this moment with the default memory limit because GD uses about 4 > > times the amount of pixels in an image as memory. > > To be honest, I've never understood why. php_imlib2 seems to run though > things fine with large files, and the structure of that is hardly > uncommon, and it's not like I've been doing anything dodgy with fudging > the zend api to get it to work right.
It was changed for a reason, that is that people could GD to crash servers quite easily. Removing this restriction is not an option. Derick