From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 09:01:30 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1C2F30C; Tue, 31 Mar 2015 09:01:30 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A4C8B7B; Tue, 31 Mar 2015 09:01:29 +0000 (UTC) Received: from [192.168.0.7] (cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61]) (authenticated bits=0) by theravensnest.org (8.15.1/8.14.9) with ESMTPSA id t2V8rqK8085863 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Mar 2015 09:01:23 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61] claimed to be [192.168.0.7] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Compiling LLDB From: David Chisnall In-Reply-To: Date: Tue, 31 Mar 2015 09:41:49 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <9A38D7D9218ED246802DA890D11AF6120EF108@wtl-exchp-1.sandvine.com> To: Ed Maste X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-toolchain@freebsd.org" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 09:01:31 -0000 On 31 Mar 2015, at 02:53, Ed Maste wrote: >=20 > I'd suggest checking /var/log/messages for further information. Is > this i386 or amd64, how much memory does your build host have, and are > you compiling with debug information or no? If had to guess, you're > running out of memory (or running into ulimit) during linking, and the > process is being killed as a result. Ninja defaults to using a large number of concurrent processes, which = can exacerbate this. If you are on a 32-bit system, or only have 4GB or = so of RAM (or have <2GB per core), you may want to explicitly do ninja = -j1 to get a serial build. Your best bet is probably something like: $ ninja -k100 $ ninja -j1 The first will do a parallel build of everything that doesn't crash. = The second will do a serial build of whatever's left. It's also = possible to configure different pools for Ninja, though I'm not sure = that this is exposed via the CMake interface yet. This mechanism exists = to allow you to say things like 'only run one link job at a time', which = can improve matters. You may also find that using gold from ports (or = possibly lld, which I believe can now link lldb) will improve matters. David