From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3440 Path: news.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: llvm-3.3 memory exhausted error Date: Tue, 18 Jun 2013 15:42:06 +0200 Message-ID: <20130618134206.GK6548@port70.net> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1371562941 8789 80.91.229.3 (18 Jun 2013 13:42:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Jun 2013 13:42:21 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3444-gllmg-musl=m.gmane.org@lists.openwall.com Tue Jun 18 15:42:20 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1UowAs-00022S-RN for gllmg-musl@plane.gmane.org; Tue, 18 Jun 2013 15:42:18 +0200 Original-Received: (qmail 17745 invoked by uid 550); 18 Jun 2013 13:42:18 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 17737 invoked from network); 18 Jun 2013 13:42:18 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3440 Archived-At: * plan9assembler [2013-06-18 22:03:53 +0900]: > Linking Debug+Asserts executable clang > /llvm-build/Debug+Asserts/lib/libLLVMCodeGen.a: could not read symbols: > Memory exhausted > collect2: error: ld returned 1 exit status > ... gnu ld ran out of memory as usual (i dont think this issue is musl related) google had the same problem so they wrote the gold linker (you can try that, it's in binutils) you can also try the magic flags -Wl,--no-keep-memory,--reduce-memory-overheads (this will make linking even slower) you can try to run ld under valgrind to see if there are leaks and report the bugs to binutils alternatively buy more ram or report the bug to llvm that their code is too bloated