similar to: [LLVMdev] Building libLLVMSupport library - special tricks?

Duncan, Many thanks for your comments. The core issue we're running into is this: $ GCC=/usr/bin/gcc LLVM_CONFIG=/usr/bin/llvm-config make Compiling utils/TargetInfo.cpp Linking TargetInfo ld: fatal: library -lLLVMSupport: not found ld: fatal: file processing errors. No output written to TargetInfo collect2: error: ld returned 1 exit statusAll other gyrations are attempts to shoehorn

LLVM Friends, First time attempting a build of dragonegg, using our shiny new install of clang-3.3. I'm clearly off to a terrifying start! dragonegg-3.3.src$ CXX=/usr/bin/gcc GCC=/usr/bin/gcc ENABLE_LLVM_PLUGINS=1 LLVM_CONFIG=/usr/bin/llvm-config CFLAGS=-I/usr/clang/3.3/lib/clang/3.3/include CXXFLAGS="-I/usr/clang/3.3/lib/clang/3.3/include" make Compiling

That did it, thanks for the help! For the future is there a set of documentation for these bindings, or their equivalent c functions? I tried looking but was having trouble finding anything that seemed to match. On Wed, Jun 29, 2016 at 1:35 AM Andrew Wilkins <axwalk at gmail.com> wrote: > On Wed, 29 Jun 2016 at 00:32 Brian Picciano via llvm-dev < > llvm-dev at lists.llvm.org>

Recently I started getting these warnings - thousands of them - and I'm not sure what I did to cause them or how to solve them: ld: warning llvm::MemoryBuffer::getBufferStart() const has different visibility (1) in /usr/local/lib/libLLVMSupport.a(MemoryBuffer.o) and (2) in /usr/local/lib/libLLVMSupport.a(CommandLine.o) ld: warning

http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-August/016763.html On 2008-09-05, at 22:46, Talin wrote: > Recently I started getting these warnings - thousands of them - and > I'm > not sure what I did to cause them or how to solve them: > > ld: warning llvm::MemoryBuffer::getBufferStart() const has different > visibility (1) in

On Wed, 29 Jun 2016 at 00:32 Brian Picciano via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I have the following code to generate a really basic IR: > http://gobin.io/LtdJ > > And the output I get from it is: http://gobin.io/XgkH > > That IR code which is dumped seems to work fine if I do llc then gcc on > it, so I'm not sure why it won't work through the

I am getting below error when running "configure --with-ldap --with-ldapsam --with-ads":

This is compiling the Trunk revision from last Friday: reference out of range from _llvm_regerror (1000437F0) in ../../lib/libLLVMSupport.a(regerror.c.o) to cstring=0 (0) in ../../lib/libLLVMSupport.a(regerror.c.o) ld: rel32 out of range in _llvm_regerror from ../../lib/libLLVMSupport.a(regerror.c.o) clang-3: error: linker command failed with exit code 1 (use -v to see invocation) OS X 10.6,

Hi, Recent trunk has a lot of failures on PPC64/Linux. One seems to be crash with a backtrace like: [ 3149s] -- [ 3149s] 0 libLLVMSupport.so 0x00003fff7ed0b864 llvm::sys::PrintStackTrace(_IO_FILE*) + 4294746876 [ 3149s] 1 libLLVMSupport.so 0x00003fff7ed0bb1c [ 3149s] 2 libLLVMSupport.so 0x00003fff7ed0c520 [ 3149s] 3 linux-vdso64.so.1 0x00003fff7f7b0478 __kernel_sigtramp_rt64 + 0 [ 3149s] 4

I was a bit confused with what the difference was between the old target_link_libraries(foo bar) and the new target_link_libraries(foo INTERFACE|PRIVATE|PUBLIC bar) To try to find out, I decided to look at the generated build.ninja. The difference that shows up is far fewer order only dependencies. For example build lib/TableGen/CMakeFiles/LLVMTableGen.dir/Error.cpp.o: CXX_COMPILER

Hi, I'm getting a returning build failure when building a linux->windows crosscompiler out of LLVM/Clang. Attached is config.log and below is the output of "make VERBOSE=1" llvm[2]: Linking Release executable FileCheck (without symbols) g++ -I/home/ruben/mingw-w64/toolchain/linux64mingw64/llvm-clang/include

Hi Ruben, Try adding a --build=x86_64-gnu-linux option to configure as well. I don't have that configuration locally, so I can't check to be certain, but IIRC, our configure wants all three for a cross compile like this. -Jim On Aug 21, 2011, at 7:19 AM, Ruben Van Boxem wrote: > Hi, > > I'm getting a returning build failure when building a linux->windows >

----- Original Message ----- > From: "Renato Golin" <renato.golin at linaro.org> > To: "İsmail Dönmez" <ismail at donmez.ws> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Wednesday, March 26, 2014 8:14:18 AM > Subject: Re: [LLVMdev] Lots of regtest failures on PPC64/Linux > > Hi Ismail, > > Is

thanks for the reply ..I tried building it from outside ...but got a similar error .. # ls /llvm/src ==> src directory llvm-3.1.src # pwd /llvm/build ==> build directory #gmake libs-only ... ... gmake[2]: Leaving directory `/llvm/build/lib/DebugInfo' gmake[1]: Leaving directory `/llvm/build/lib' gmake[1]: Entering directory `/llvm/build/tools/llvm-config'

Hi, On the OpenMandriva side, x86_64 passes all checks. We're having some problems with other architectures though (see below): x86_64 succeeded, packages are here: https://abf.openmandriva.org/build_lists/76792 i586 fails to build, but this seems to be an issue with 3.8.1 (which we're using to build 3.9): /usr/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS

Michael, I'm looking at flushing out the mach-o driver and targetinfo. Can we rename the "ld64" flavor to "darwin". The command line tool on MacOSX is called "ld" - just like on unix. The name ld64 is the current source repository name for the linker. Once lld takes over, the term ld64 won't mean anything. I've worked through adding DarwinOpts.td

Hi, I'm cross compiling (BUILD=darwin, HOST=i386-mingw32) LLVM with llvm-gcc (both from current mainline). Everything works fine, except that I get a lot of warnings of the following type: [..]/lib/gcc/i386-mingw32/4.2.1/../../../../i386-mingw32/bin/ld: /[..]/build-llvm/Release/lib/libLLVMSupport.a(APInt.o): warning: duplicate section `.text$linkonce__ZN4llvm5APInt17getSignedMinValueEj'

I'm trying to make a library in Xcode that links against LLVM. I used the STL C++ template in Xcode 4.5.2, added libLLVMCore.a and libLLVMSupport.a to the link binaries phase, and made this call in my code: llvm::LLVMContext& llvmCTX = llvm::getGlobalContext(); I get link errors against std::string and other STL classes: Undefined symbols for architecture x86_64:

I was wandering how much is the overhead of virtual function calls of TargetInfo member functions. TargetInfo handles platform-specific details, and we have target-specific subclasses of that class. The subclasses override functions defined in TargetInfo. The TargetInfo member functions are called multiple times for each relocation. So the cost of virtual function calls may be non-neglible. That

I believe the relocation stuff that Rafael is currently working on will make this a non-issue (it will make relocation application much friendlier for the CPU). However, even in the current scheme, since the target is fixed, all the indirect call sites should be monomorphic and so there shouldn't be much branch-prediction cost (certainly nothing that would cause 1.8% performance delta for the