+1 for removing. I've been wanting to do that for a while now...
>>
>> Looking at the other duplicated tests, we have the potential for similar
>> issues. They also all use CHECK rather then CHECK-DAG, so we should at least
>> update them to use CHECK-DAG.
Could you elaborate on this? I don't s
Dear folks,
I am trying to build & install LLVM, Clang and LLDB from source. Now the
build completes fine, while the target `install' fails:
-- Up-to-date: /opt/llvm/6.0.1/include/lldb/Host/Config.h
CMake Error at tools/lldb/scripts/cmake_install.cmake:41 (file):
file INSTALL cannot find "/opt/
When I do a build on Linux, in /lib I see a directory called python2.7,
with a subdirectory site-packages. Do you not see this?
Are you building with a different python version than 2.7.x?
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora
Indeed that folder is not present. Python 2.7 is installed and it is the
default version of the system, I'm not changing its setting in the build.
On 18/07/18 18:19, Ted Woodward wrote:
When I do a build on Linux, in /lib I see a directory called
python2.7, with a subdirectory site-packages.
It should be built by the “lldb” target. What does that do?
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of
Quaquaraqu
I have a very simple testcase, from the libc++ tests. get_id.pass.cpp.
#include
#include
int main()
{
std::thread::id id = std::this_thread::get_id();
std::thread::id id2 = std::thread::id();
assert(id != std::thread::id());
}
I built it with clang 3.8.0. I get the crash when I bui
the target is built fine, with no warnings or other related messages. I
tried to dig a bit, but I wasn't able to understand how it is supposed
to be built . The only refs I've found are inside lldbUtility, protected
by a guard on LLVM_BUILD_STATIC which does seem to be defined nowhere,
and scri
