Thank you for the quick reply. Indeed, that appeared to be the issue. For others who may see this (or similar) -
My system has 1GB core and 1GB swap. Today I did a clean boot and monitored the build. I enabled the same options as yesterday, including the profiling. During the first part of the build, swap use maxed out about 750MB. Subsequently, the profile build ran its tests, closed and the new build continued. Watching closely, I saw swap top out at 964MB and then fall off dramatically from that point. I know there was an IM application open last night as well as a few additional xterms. I'm guessing those were enough to have pushed the swap usage just over 1GB and thus crash the build. Of additional note: When I dropped out of X this morning and back to the regular console, I did see an out of memory error (or similar wording to that effect). This did not show up while running via xterm and I never thought to look at any logs as the profiling build of firefox had been successful, To give a cushion today (as the build takes forever), I prepared a temporary swapfile and enabled that while doing the build. Bottomline: you need just over 2GB to build the firefox 9 port successfully. ________________________________ From: "f...@freebsd.org" <f...@freebsd.org> To: birdf...@yahoo.com; f...@freebsd.org; ge...@freebsd.org Sent: Sunday, January 29, 2012 6:55 AM Subject: Re: ports/164594: www/firefox 9 is broken Synopsis: www/firefox 9 is broken This is usually an indication that you don't have enough free memory/swap space to build firefox. How much memory does you system have? http://www.freebsd.org/cgi/query-pr.cgi?pr=164594 _______________________________________________ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
