From owner-freebsd-ports@FreeBSD.ORG Thu Mar 3 07:40:16 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 402EB16A4D5; Thu, 3 Mar 2005 07:40:16 +0000 (GMT) Received: from smradoch.ath.cx (r2g224.chello.upc.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8275543D5A; Thu, 3 Mar 2005 07:40:15 +0000 (GMT) (envelope-from neuhauser@chello.cz) Received: by smradoch.ath.cx (Postfix, from userid 1001) id 2F0351F87BEE; Thu, 3 Mar 2005 08:40:15 +0100 (CET) Date: Thu, 3 Mar 2005 08:40:15 +0100 From: Roman Neuhauser To: ale@freebsd.org Message-ID: <20050303074015.GA704@isis.wad.cz> Mail-Followup-To: ale@freebsd.org, ports@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i cc: ports@freebsd.org Subject: lang/php4-cli: --enable-memory-limit in CONFIGURE_ARGS? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 07:40:16 -0000 Hello, can the lang/php4 port be modified so that the cli version of php is configured without --enable-memory-limit in CONFIGURE_ARGS? It only makes sense in the apache/cgi SAPIs, and is quite strange in a command line tool (twice so with the default limit of 8MB). A workaround is to set the limit in php-cli.ini to a very high number, but there's still a (small) performance impact. -- FreeBSD 4.10-STABLE 8:26AM up 32 mins, 3 users, load averages: 0.00, 0.00, 0.00