[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130618134206.GK6548@port70.net>
Date: Tue, 18 Jun 2013 15:42:06 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: llvm-3.3 memory exhausted error
* plan9assembler <plan9assembler@...il.com> [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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
