It seems that test-release was fixed, thanks everyone. Builds are OK but
I'd like to know where did test-suite go? All I see is the llvm.src
directory, am I supposed to export test-suite myself?
On Wed, Jan 27, 2016 at 9:47 PM, Daniel Sanders
wrote:
> > Have you accidentally checked out the test
https://llvm.org/bugs/show_bug.cgi?id=26339
Bug ID: 26339
Summary: TestCPPAuto.py fails on Windows
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Prio
Hi Pavel,
Will is trying to get this working downstream of here IIRC.
Greg, can you have a look and see what you think of the patch? (Also see
Pavel's comments).
Thanks!
-Todd
On Wed, Jan 27, 2016 at 1:28 AM, Omair Javaid via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hi Will,
>
> I dont u
Okay. I'm stuck fixing the OS X build, but if you have something else to
check, feel free to send it over my way and I can run it on another machine.
On Tue, Jan 26, 2016 at 7:52 PM, Zachary Turner wrote:
> Humm.. it's a unicode literal, not sure why it's complaining. I guess
> I'll have to c
Hi all,
At the current moment the OS X Xcode build is broken. I'll be working on
fixing it today. As has been discussed in the past, post llvm/clang-3.8
the configure/automake system was getting stripped out of LLVM and clang.
The OS X Xcode build has a legacy step in it that still uses the
conf
https://llvm.org/bugs/show_bug.cgi?id=26335
lab...@google.com changed:
What|Removed |Added
CC||lab...@google.com
Assignee|lldb-de
> Have you accidentally checked out the test-suite into /projects? if it's
> there it will auto-configure
We fixed it for rc1 but test-release.sh used to put the test-suite there.
From: llvm-dev [mailto:llvm-dev-boun...@lists.llvm.org] On Behalf Of James
Molloy via llvm-dev
Sent: 26 January 201
https://llvm.org/bugs/show_bug.cgi?id=26335
Bug ID: 26335
Summary: lldb (after 3.7.x) compilation fails at link-time with
shared library
Product: lldb
Version: 3.8
Hardware: PC
OS: Linux
Status:
Hi Will,
I dont understand REPL and thus the benefits it will have by making
change to architecture name. I would not recommend to drop any
information that we get from the host operating system.
LLDB maintains core information alongwith triple in ArchSpec, may be
you can parse triple to reflect
https://llvm.org/bugs/show_bug.cgi?id=23039
abhiinnit...@gmail.com changed:
What|Removed |Added
CC||abhiinnit...@gmail.com
Assign
https://llvm.org/bugs/show_bug.cgi?id=19311
abhiinnit...@gmail.com changed:
What|Removed |Added
CC||abhiinnit...@gmail.com
Assign
11 matches
Mail list logo
