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
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:
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
https://llvm.org/bugs/show_bug.cgi?id=27861
Bug ID: 27861
Summary: TestObjCMethods2.py -
test_NSString_expr_commands_gmodules() fails
Product: lldb
Version: unspecified
Hardware: PC
OS: MacOS X
S
https://llvm.org/bugs/show_bug.cgi?id=27862
Bug ID: 27862
Summary: TestRuntimeTypes.py test_break_gmodules() fails on OS
X
Product: lldb
Version: unspecified
Hardware: PC
OS: MacOS X
Status: NEW
https://llvm.org/bugs/show_bug.cgi?id=27863
Bug ID: 27863
Summary: TestGlobalVariables.py
test_c_global_variables_gmodules() fails on OS X
Product: lldb
Version: unspecified
Hardware: PC
OS: MacOS X
https://llvm.org/bugs/show_bug.cgi?id=27863
Todd Fiala changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=27864
Bug ID: 27864
Summary: TestTopLevelExprs.py
test_top_level_expressions_gmodules() fails on OS X
Product: lldb
Version: unspecified
Hardware: PC
OS: MacOS X
Meant to send this yesterday, but I want to remind everyone that we’re going to
be raising the CMake minimum version to 3.4.3 next week.
If you maintain bots please ensure that your bots are updated by end of day
5/29 so that we can move on 5/30 (next Monday).
I have already heard from most bot
Upgraded the libc++ bots.
On Tue, May 24, 2016 at 2:54 PM, Chris Bieneman via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> Meant to send this yesterday, but I want to remind everyone that we’re
> going to be raising the CMake minimum version to 3.4.3 next week.
>
> If you maintain bots please ensur
https://llvm.org/bugs/show_bug.cgi?id=27865
Bug ID: 27865
Summary: DeadStripTest.py test_gmodules() fails on Linux x86_64
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: nor
https://llvm.org/bugs/show_bug.cgi?id=27868
Bug ID: 27868
Summary: Evaluating JITed expressions on arm cannot handle hard
float ABI
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Statu
On 24.05.2016 22:54, Chris Bieneman via lldb-dev wrote:
> Meant to send this yesterday, but I want to remind everyone that we’re going
> to be raising the CMake minimum version to 3.4.3 next week.
>
> If you maintain bots please ensure that your bots are updated by end of day
> 5/29 so that we c
http://lab.llvm.org:8011/builders/lldb-amd64-ninja-netbsd7/builds/4296
It looks like after this build, scripts for bots were altered to require
clang + clang++? I'm using the GNU toolchain. Could we please revert
this enforcement?
___
lldb-dev mailing li
There's no CMake change in any of these patches. It looks like something
is wrong with your bot.
On Tue, May 24, 2016 at 5:14 PM Kamil Rytarowski via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> http://lab.llvm.org:8011/builders/lldb-amd64-ninja-netbsd7/builds/4296
>
> It looks like after this b
There is a change in build scripts from buildbot farm:
+ cmake -GNinja -DCMAKE_BUILD_TYPE=Release
/home/motus/build/build/scripts/../llvm -DCMAKE_C_COMPILER=clang
-DCMAKE_CXX_COMPILER=clang++
A commit earlier it was:
+ cmake -GNinja -DCMAKE_BUILD_TYPE=Release
/home/motus/build/build/scripts/../l
16 matches
Mail list logo
