From owner-freebsd-ports@FreeBSD.ORG Fri Dec 31 21:33:06 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1A581065694 for ; Fri, 31 Dec 2010 21:33:06 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4278E8FC0C for ; Fri, 31 Dec 2010 21:33:05 +0000 (UTC) Received: by bwz12 with SMTP id 12so5258630bwz.13 for ; Fri, 31 Dec 2010 13:33:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:received :reply-to:in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=He43XaQc1+UGRTHepDP993fzs2laQ1kaSPT7U89ei/U=; b=LaEC7tgt0nti8ZjBqZ6V2zQWGUF36J+bFqyJTYftAXvpOeMUVOA/COD50TRlbiSTND 6Rxk8bIzR+/jcWVFUa8Sjl1H7sw4BGSM668GWoXYkG3F3R9Pr/KuolwA4Rm4s7XaUPde WbQ6Rzrg1AOeJmMgekmeNfdpKxYWr/GTMa9U0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=bc3+x3N32M5VBe6kalj8ydHeuxDyUVm3c53VfG1DVcLMxR14lRhw2VOeX1Fy3LeBL4 jUUQKyXWJmGhxPMBPXpOmroZqeTiv5hlTGaUlAA4ttWns7OSTqVCMBlILBjDlG85BHnN gko/JWKf6531yPZb6yqSZxtTTZfELWSvV7E4w= MIME-Version: 1.0 Received: by 10.204.46.134 with SMTP id j6mr14077407bkf.112.1293829674147; Fri, 31 Dec 2010 13:07:54 -0800 (PST) Received: by 10.204.52.19 with HTTP; Fri, 31 Dec 2010 13:07:53 -0800 (PST) Received: by 10.204.52.19 with HTTP; Fri, 31 Dec 2010 13:07:53 -0800 (PST) In-Reply-To: <4D1D6C64.2090604@herveybayaustralia.com.au> References: <4D1B044F.6050903@herveybayaustralia.com.au> <86fwtgob5w.fsf@gmail.com> <4D1BBE7F.5060202@herveybayaustralia.com.au> <4D1CB795.5090506@DataIX.net> <4D1D6C64.2090604@herveybayaustralia.com.au> Date: Fri, 31 Dec 2010 21:07:53 +0000 Message-ID: From: Chris Rees To: Da Rock Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ports@freebsd.org Subject: Re: libxul build hit the roof! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2010 21:33:06 -0000 I would argue that anyone messing with CFLAGS should expect and know how to fix trouble like that. This would also save noise. Chris -------- Sorry for top-posting, Android won't let me quote, but K-9 can't yet do threading. On 31 Dec 2010 05:42, "Da Rock" wrote: > On 12/31/10 02:47, jhell wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 12/29/2010 18:04, Da Rock wrote: >> >>> I got it worked out in the end, but it still took 2G+ memory to build; >>> so my suggestion is a warning to EU in the make process that this could >>> take a lot of memory to build, and some suggestions as to how to prevent >>> or workaround the problem so they don't go whining on the list about it >>> being broken. >>> >> Turning off OPTIMIZED_CFLAGS for 'libxul, firefox*& thunderbird*' ports >> would have stopped all this swapping from happening. >> >> Is there a specific reason why you changed it from its defaults ? is >> there really anything to gain ? in respect to 'libxul'... >> > I see your point and I'll raise you a does it matter? There are sites > and howto's on improving performance overall, especially regarding the > revival of older machines. The recommendation on a lot of these is to > put CFLAGS+= -O -pipe in the make.conf. If they already have low memory, > then they'll be up the creek won't they? And the updates won't happen so > they'll simply be broken and unsure of why. > > I'd say a simple note to say whats up is definitely in order, to prevent > a lot of traffic. I don't believe thats too hard to do, given jdk16 and > OOO have messages reflecting HDD space. I only noticed the issue because > I watched it happen- given the little relevance that most (including > yourself) put on it, it would easily be overlooked unless a simple > solution was presented. The only message you get from say portupgrade is > new compiler error, most would then put it in the too hard basket. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"