similar to: [LLVMdev] Unable to build compiler-rt (Windows)

于 2012/8/3 17:44, Ruben Van Boxem 写道: > Hi, > > As it stands, I cannot build nor test compiler-rt. I downloaded the > latest sources from svn > (http://llvm.org/svn/llvm-project/compiler-rt/trunk) and ran > cmake ../../Source/compiler-rt -G"MinGW Makefiles" > > and got the following error: > ... > -- Detecting CXX compiler ABI info - done > CMake Error

2012/8/3 xunxun <xunxun1982 at gmail.com> > 于 2012/8/3 17:44, Ruben Van Boxem 写道: > > Hi, >> >> As it stands, I cannot build nor test compiler-rt. I downloaded the >> latest sources from svn (http://llvm.org/svn/llvm-** >> project/compiler-rt/trunk<http://llvm.org/svn/llvm-project/compiler-rt/trunk>) >> and ran >> cmake

Hi again, I'm trying to upgrade my LLVM bindings in Java from 2.9 to 3.1. To do so, I regenerated the JNI bindings from fresh LLVM 3.1 headers, and did a slight rewrite of my CMakeLists.txt file for building the C code. Problem is, cmake no longer finishes at all. I receive the following output, and then it just runs forever (while still responding to a CTRL-C): > eli at

At 167457 on x86_64-apple-darwin12, I am seeing a slew of AddressSanitizer failures due to unresolved symbols such as... Exit Code: 1 Command Output (stderr): -- Undefined symbols for architecture x86_64: "___asan_init", referenced from: _asan.module_ctor in shared-lib-test-so-moBSTe.o "___asan_register_globals", referenced from: _asan.module_ctor in

> We have plans to actually compile the symbolizer into the binary and do > in-process symbolization, but it's not there yet. nice! > I'm confused here. compiler-rt and clang/llvm instrumentation depend on each other These two projects don't need to be interdependent and, for the most part, they aren't. In the same way that llvm does not depend on clang, compiler-rt

The fix is under review. --kcc On Tue, Nov 6, 2012 at 6:08 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > At 167457 on x86_64-apple-darwin12, I am seeing a slew of > AddressSanitizer failures due to > unresolved symbols such as... > > Exit Code: 1 > Command Output (stderr): > -- > Undefined symbols for architecture x86_64: > "___asan_init",

Fix is in (r167460). On Tue, Nov 6, 2012 at 6:18 PM, Kostya Serebryany <kcc at google.com> wrote: > The fix is under review. > > --kcc > > > On Tue, Nov 6, 2012 at 6:08 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > >> At 167457 on x86_64-apple-darwin12, I am seeing a slew of >> AddressSanitizer failures due to >> unresolved symbols

On Thu, May 30, 2013 at 10:05 PM, Greg Fitzgerald <garious at gmail.com> wrote: > The sanitizer common and asan that mention 'thread' are failing for me > this morning. How are your bots looking? Last good commit here was > 512c616cacf70ca029a2bf719a482b902f3687cd. > Hm, our bots seem to be green. Could you refer to guilty svn revision? > > > You could try

The sanitizer common and asan that mention 'thread' are failing for me this morning. How are your bots looking? Last good commit here was 512c616cacf70ca029a2bf719a482b902f3687cd. > You could try preprocessing your report with perl or sed to fix paths > to your binaries. It would be great to have an option for that in > asan_symbolize.py. > > As for addr2line, we just

On Fri, Nov 02, 2012 at 06:45:07PM +0400, Alexey Samsonov wrote: > Hi, Jack! > > > I'll take a look at this. However, tests below fail for a different reason > (they don't use Debug/AsanTest at all). > How do you configure a CMake build tree? Can you somehow get (or run > manually) the script which is used > for running log-path_test.cc and other failing test

Hi, I'm building using MINGW64 on a very slow system (Intel Atom 330 X2 1.6 GHz), but it seems rather odd that the system has been linking clang.exe for the past two hours. It appears that a couple of gigabytes of virtual memory are being used (causing constant swapping) - the system has only 2 GB of physical memory. Is this a bug in MINGW64 (binutils 2.22) or is it just too little RAM in

于 2012/5/27 11:04, Mikael Lyngvig 写道: > Hi, > > I'm building using MINGW64 on a very slow system (Intel Atom 330 X2 > 1.6 GHz), but it seems rather odd that the system has been linking > clang.exe for the past two hours. It appears that a couple of > gigabytes of virtual memory are being used (causing constant swapping) > - the system has only 2 GB of physical memory.

Hi, Jack! On Fri, Nov 2, 2012 at 6:18 PM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > Nick, > Have you noticed that llvm/clang svn produces the following linker > warnings on > 'make check-all'? > > Linking CXX executable Debug/AsanTest > ld: warning: direct access in > llvm::convertible_fwd_ostream::~convertible_fwd_ostream() to global weak >

> > *hi,Óscar:* > * * > >Why? Please describe a case. > > >I need to do some futher experiment and to see whether I have been > wrong. > Since I touch this problem several months ago, so I did some test using the 3.2svn, the reason why uninstalled build 'cmake not work lies in set(LLVM_INSTALL_PREFIX @LLVM_INSTALL_PREFIX@) set(LLVM_INCLUDE_DIRS

Nick, Have you noticed that llvm/clang svn produces the following linker warnings on 'make check-all'? Linking CXX executable Debug/AsanTest ld: warning: direct access in llvm::convertible_fwd_ostream::~convertible_fwd_ostream() to global weak symbol vtable for llvm::convertible_fwd_ostream means the weak symbol cannot be overridden at runtime. This was likely caused by different

> > Replicating ExternalProject would be a lot of work... > One approach commonly used with CMake modules that change frequently upstream is for the project to keep a local copy and have a check in place to use CMake's version if new enough. For instance, in llvm's source tree: cmake/modules/ExternalProject.cmake: if(CMAKE_VERSION VERSION_LESS "3.5.1")

hume npx <humeafo at gmail.com> writes: Sorry for commenting the bug report here, but I can't loging to bugzilla right now. > Using cmake should be the right thing if you'd like to support windows, but > it seems that no enough effort on this build system, eg > http://llvm.org/bugs/show_bug.cgi?id=12157 three months passed, There is indeed a problem with the value

Hi Timo: You need to find LLVMConfig.cmake in the binary or install directory tree, not the source tree. Although I don't embed clang/llvm, my config might help you figure it -- clang/llvm installed under (could have used build directory) ~/usr : $ cd /Users/dhinton/projects/cover/build/ && rm -rf * && CC=~/usr/bin/clang CXX=~/usr/bin/clang++ LLVM_DIR=~/usr/lib/cmake/llvm

Hi, Óscar: nice to hear some voice on this. about LLVM_TOOLS_BINARY_DIR, yes, it made the installed version work only, if you'd like the uninstalled version to work, it should be detected as you suggested. about LLVM_INSTALL_PREFIX the purpose is to make it really relocatable, eg, when installed under /lib/llvm I just later need to move the installation tree to /lusr/local/lib/llvm

*hi,Óscar:* * * *so following patch should address both the relocation problem and uninstall tree problem, not fully tested just for discussion.* * * Index: LLVMConfig.cmake.in =================================================================== --- LLVMConfig.cmake.in (revision 159425) +++ LLVMConfig.cmake.in (working copy) @@ -32,8 +32,11 @@ set(LLVM_ON_WIN32 @LLVM_ON_WIN32@)