Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:10891 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90552 invoked by uid 1010); 3 Jul 2004 22:10:08 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 90431 invoked from network); 3 Jul 2004 22:10:08 -0000 Received: from unknown (HELO stack.fission.org.uk) (195.82.120.217) by pb1.pair.com with SMTP; 3 Jul 2004 22:10:08 -0000 Received: from cpc4-oxfd3-3-0-cust191.oxfd.cable.ntl.com ([213.107.70.191] helo=[192.168.10.254]) by stack.fission.org.uk with esmtp (Exim 3.36 #1 (Debian)) id 1Bgsfc-0007PG-00; Sat, 03 Jul 2004 23:07:40 +0100 To: Derick Rethans Cc: internals@lists.php.net In-Reply-To: References: <5.1.0.14.2.20040623142947.03cca8e0@localhost> <5.1.0.14.2.20040623142947.03cca8e0@localhost> <5.1.0.14.2.20040623170721.048dca08@localhost> Content-Type: text/plain Message-ID: <1088892609.2185.61.camel@mesa> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 03 Jul 2004 23:10:09 +0100 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] 'make install' fails when --enable-memory-limit is present From: gareth@fission.org.uk (Gareth Ardron) 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.