Date: Mon, 30 Mar 2015 21:53:19 -0400 From: Ed Maste <emaste@freebsd.org> To: Kenan Ali <kali@sandvine.com> Cc: "freebsd-toolchain@freebsd.org" <freebsd-toolchain@freebsd.org> Subject: Re: Compiling LLDB Message-ID: <CAPyFy2BRot1qeFjnPgE_h3cXvewCTpXU4zBdQ0EpSESpE%2BBAqQ@mail.gmail.com> In-Reply-To: <9A38D7D9218ED246802DA890D11AF6120EF108@wtl-exchp-1.sandvine.com> References: <9A38D7D9218ED246802DA890D11AF6120EF108@wtl-exchp-1.sandvine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 March 2015 at 19:18, Kenan Ali <kali@sandvine.com> wrote: > Hi, > > I would like to see if I could get involved with contributing to the kern= el core support for LLDB under FreeBSD. I'm running a FreeBSD-head build (o= n a VM) from a week or two ago, and I'm following the instructions from her= e: https://wiki.freebsd.org/lldb > > Once I get to the 'ninja lldb' step, it seems that I always end up with t= he following error: > > CC: error: unable to execute command: Killed > CC: error: linker command failed due to signal (use -v to see invocation) > Ninja: build stopped: subcommand failed. > > I've tried passing the '-v' flag to ninja, which lists a large invocation= before spewing out the errors above. However, I cannot seem to figure out = how to get the '-v' command passed to LLVM's linker. Neither ninja's help o= utput or some basic Googling seem to be helping me diagnose this issue, so = I was wondering if anyone here could help? 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2BRot1qeFjnPgE_h3cXvewCTpXU4zBdQ0EpSESpE%2BBAqQ>