From owner-freebsd-arm@freebsd.org Mon Oct 5 12:58:49 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 216EA9B609E for ; Mon, 5 Oct 2015 12:58:49 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (kientzle.com [142.254.26.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D6F49BE1 for ; Mon, 5 Oct 2015 12:58:48 +0000 (UTC) (envelope-from tim@kientzle.com) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t95CxKlW047047; Mon, 5 Oct 2015 12:59:20 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.108] (192.168.1.101 [192.168.1.101]) by kientzle.com with SMTP id i3yptxb5bbvfwzcg7rxyxawpe6; Mon, 05 Oct 2015 12:59:20 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: build kernel on RPI2 errors From: Tim Kientzle In-Reply-To: <5611F005.60201@kronometrix.org> Date: Mon, 5 Oct 2015 05:58:40 -0700 Content-Transfer-Encoding: 7bit Message-Id: <10CB4F8C-3F30-45EE-921F-C6E3981EC01F@kientzle.com> References: <5611F005.60201@kronometrix.org> To: freebsd-arm X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2015 12:58:49 -0000 > On Oct 4, 2015, at 8:35 PM, Stefan Parvu wrote: > > cc: error: unable to execute command: Killed > cc: error: clang frontend command failed due to signal (use -v to see > invocation) I wonder if this error message could be any better? It's such a common issue on these small-memory systems. Is it possible for 'cc' to detect whether clang died due to an out-of-memory condition and print out a slightly more detailed message in that case? Tim