From owner-freebsd-gecko@FreeBSD.ORG Fri Mar 4 16:19:54 2011 Return-Path: Delivered-To: gecko@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACFE7106566B for ; Fri, 4 Mar 2011 16:19:54 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 462478FC1E for ; Fri, 4 Mar 2011 16:19:54 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 035F7C; Fri, 4 Mar 2011 17:06:13 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Fri, 04 Mar 2011 17:04:48 +0100 From: Bernhard Froehlich To: "Sergey V. Dyatko" In-Reply-To: <20110304150926.2237d6df@tiger.minsk.domain> References: <20110304150926.2237d6df@tiger.minsk.domain> Message-ID: <688ae028915f448c391bb25cba201f64@bluelife.at> X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.5.1 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0205.4D710D9F.0122,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: gecko@freebsd.org Subject: Re: unable to build www/libxul X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 16:19:54 -0000 On Fri, 4 Mar 2011 15:09:26 +0200, Sergey V. Dyatko wrote: > Hi, > > I'm trying update www/libxul but got following error: > http://tiger.ipfw.ru/files/libxul.txt > > tiger# uname -a > FreeBSD tiger.minsk.domain 9.0-CURRENT FreeBSD 9.0-CURRENT #33 r217684: > Fri Jan 21 11:46:03 EET 2011 > root@tiger.minsk.domain:/usr/obj/usr/src/sys/tiger-desktop i386 > > [tiger@tiger]~%pkg_version -vL=|grep xul > libxul-1.9.2.13 < needs updating (port has > 1.9.2.14) c++: Internal error: Killed: 9 (program cc1plus) That means gcc was killed with signal 9 and that is SIGKILL. Probably /var/log/messages tells you more. It could be possible that the system runs out of swap and thus gcc gets killed by the out of memory killer. -- Bernhard Froehlich http://www.bluelife.at/