Date: Tue, 6 Oct 2015 18:45:31 +0200 From: Bernd Walter <ticso@cicely7.cicely.de> To: Tim Kientzle <tim@kientzle.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: build kernel on RPI2 errors Message-ID: <20151006164531.GB89482@cicely7.cicely.de> In-Reply-To: <10CB4F8C-3F30-45EE-921F-C6E3981EC01F@kientzle.com> References: <5611F005.60201@kronometrix.org> <10CB4F8C-3F30-45EE-921F-C6E3981EC01F@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 05, 2015 at 05:58:40AM -0700, Tim Kientzle wrote: > > > On Oct 4, 2015, at 8:35 PM, Stefan Parvu <sparvu@kronometrix.org> 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? The kernel message is quite clear. Wonder why it became so uncommon over the last years to check dmesg. -- B.Walter <bernd@bwct.de> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151006164531.GB89482>