I had similar problems on NetBSD/amd64 - using standalone builds helped
me. I'm building and installing LLVM, Clang and LLDB separately. It may
help on i386.
Also there might be a problem with using too many jobs. Try to build
with -j1.
On 24.05.2016 20:01, Siva Chandra via lldb-dev wrote:
> We h
We hit similar problems in the past when building with debug info
enabled; using -gsplit-dwarf helped us.
On Sun, May 22, 2016 at 3:36 AM, Sylvestre Ledru via lldb-dev
wrote:
> Hello,
>
> Lately, I haven't been able to link lldb because it uses too much memory:
>
> /usr/bin/ld: final link failed:
Is it only lldb-server you are having problems with? (i.e., are you
able to link liblldb.so?)
If so, then you might be able to make it link by reducing the number
of things that go into it. Right now lldb-server uses only a fraction
of its linker input, but we still need to pass in everything (and
cross building on a 64-bit machine using a 64-bit toolchain is what we have
to do on Windows.
On Mon, May 23, 2016 at 2:21 PM Greg Clayton via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Don't generate debug info would be one that comes to mind. The other is to
> cross build for i386 on a 64 bit
Don't generate debug info would be one that comes to mind. The other is to
cross build for i386 on a 64 bit machine.
Greg
> On May 22, 2016, at 3:36 AM, Sylvestre Ledru via lldb-dev
> wrote:
>
> Hello,
>
> Lately, I haven't been able to link lldb because it uses too much memory:
>
> /usr/bi
Hello,
Lately, I haven't been able to link lldb because it uses too much memory:
/usr/bin/ld: final link failed: Memory exhausted
As reported here:
https://llvm.org/bugs/show_bug.cgi?id=27237
(yes, I use shared libraries)
Any workaround?
Thanks,
Sylvestre
PS: please cc me !
_
