similar to: [LLVMdev] Cannot Compile through an LLVM Pass

I get compile errors for just including the "clang/Basic/Diagnostic.h" header file. Is that expected? Should I include anything else? Here are the errors: $ g++ main.cpp -I llvm/tools/clang/include -I llvm/include In file included from llvm/include/llvm/Support/PointerLikeTypeTraits.h:18, from llvm/tools/clang/include/clang/Basic/SourceLocation.h:17,

Hi I’m having a few problems building the kaleidoscope example (chapter 3) under MinGW. To build the example I use as recommended g++ -g -O3 toy.cpp `llvm-config --cppflags --ldflags --libs core` -o toy but get the following error sh: llvm-config: command not found Indeed in my “\llvm-2.7\tools\llvm-config\” build directory there is no “Release” subdirectory as I would expect (only

Hi Ashok, I created a new Ubuntu 12.04 virtual machine and followed directions except that I know use your cmake command instead of configure, and I got the error below. Any help is very much appreciated. $ /home/ubuntu/bin/bin/clang++ -I /home/ubuntu/bin/include/ tutorial1.cpp In file included from tutorial1.cpp:5: In file included from /home/ubuntu/bin/include/llvm/Support/raw_ostream.h:17:

Hello all, I'm trying to include and use the Module.h class into my project I get these 5 errors when I attempt to compile a cpp file that has #include <llvm/Module.h> (through eclipse) Description Resource Path Location Type #error "Must #define __STDC_CONSTANT_MACROS before " "#including System/DataTypes.h" template line 49, external

OK.  Thanks.  I now get the following error (which appears to be a problem w/ the tutorial itself?): $ /home/ubuntu/bin/bin/clang++ -I /home/ubuntu/bin/include/  -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS tutorial1.cpp/tmp/tutorial1-LQ71fW.o: In function `main': tutorial1.cpp:(.text+0x42): undefined reference to `llvm::outs()' tutorial1.cpp:(.text+0x72): undefined reference to

Add -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS to your compilation flag. On 7/10/2012 11:23 AM, NY Knicks Fan wrote: > Hi Ashok, > > I created a new Ubuntu 12.04 virtual machine and followed directions > except that I know use your cmake command instead of configure, and I > got the error below. > > Any help is very much appreciated. > > > $

Hi Ashok, $ cd bin/bin $ ./llvm-config --ldflags --libs -L/home/ubuntu/bin/lib   -ldl -lpthread -lLLVMAsmParser -lLLVMTableGen -lLLVMDebugInfo -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMJIT -lLLVMMCDisassembler -lLLVMMCParser -lLLVMInstrumentation -lLLVMInterpreter

You will need to link to the LLVM/clang libraries. To get the correct flags, you can run: ./llvm-config --ldflags --libs and use the flags reported. On 7/10/2012 11:35 AM, NY Knicks Fan wrote: > OK. Thanks. I now get the following error (which appears to be a > problem w/ the tutorial itself?): > > $ /home/ubuntu/bin/bin/clang++ -I /home/ubuntu/bin/include/ >

In the llvm file include/llvm/Support/DataTypes.h (.in/.cmake), for MSVCit defines some macros that are defined in the cstdint.hpp file in boost (and boost does it better, detailed below): The basic error is: R:\SDKs\boost\built_head\include\boost-1_38\boost/cstdint.hpp(347) : warning C4005: 'INT8_C' : macro redefinition

You need to link in the libclang* as well. On 7/10/2012 1:22 PM, NY Knicks Fan wrote: > Hi Ashok, > > $ cd bin/bin > $ ./llvm-config --ldflags --libs > -L/home/ubuntu/bin/lib -ldl -lpthread > -lLLVMAsmParser -lLLVMTableGen -lLLVMDebugInfo -lLLVMX86Disassembler > -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter > -lLLVMX86Desc -lLLVMX86Info

In DataTypes.h starting on line 121 are these lines: #define INT8_C(C) C #define UINT8_C(C) C #define INT16_C(C) C #define UINT16_C(C) C #define INT32_C(C) C #define UINT32_C(C) C ## U #define INT64_C(C) ((int64_t) C ## LL) #define UINT64_C(C) ((uint64_t) C ## ULL) They are conflicting with the cstdint when we have updated headers in our MSVC build. I could have sworn I talked about this

On 3/4/20 9:17 AM, Richard W.M. Jones wrote: > Plugins and filters may call this to initiate an asynchronous shutdown > of the server. This would only be used in the connected phase — > plugins should still call exit(3) directly for configuration failure. > > It is equivalent to sending a kill signal to self, but it's cleaner to > have an API for this and better for

Previously these were rather small - just 500 MB. This is too small to create a btrfs device on aarch64 (where page size may be 64K), and barely enough even on x86-64. This change makes both these devices 10 GB, and adjusts a few tests so they continue to pass. --- docs/guestfs-hacking.pod | 4 ++-- generator/actions.ml | 17 +++++++++++------ tests/c-api/tests-main.c | 6 +++--- 3 files

Looks like your make/install is incomplete wrt clang. I follow the instuctions for checking out the sources but build using cmake instead of configure: > cmake -G ""Unix Makefiles" -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_BUILD_TYPE="Release" -DCMAKE_INSTALL_PREFIX="../bin" ../llvm > make install This builds and installs llvm+clang in the bin

I followed the instructions in llvm_gcc's README.LLVM file, but not exactly the same. the following is what I have done with LLVM: ./configure --disable-optimized --enable-checking make make install (Successful) now the llvm-gcc: cd /home/username mkdir obj mkdir install cd obj ../llvm-gcc/configure --prefix=`pwd`/../install --program-prefix=llvm- --enable-llvm=/home/username/llvm-2.7/Debug

You need to manually copy the llvm-gcc front-end binaries to somewhere in your path. Alternatively, you can download the clang front-end and start using that instead. On Mon, Apr 19, 2010 at 10:58 AM, khaled hamidouche <khaledhamidouche at gmail.com> wrote: > Hello > > I'm trying to install LLVM and LLVM GCC > so I check out  the source of llvm and llvm-gcc-4.2 from the svn

Óscar Fuentes <ofv at wanadoo.es> writes: >> It appears the Windows build has regressed over the past week. >> >> The build fails quite early (during the "Performing TableGenStep" >> phase). >> >> Any help/pointers would be appreciated. > > It breaks for me because the usage of INT64_C, which was introduced on > r57663 and 57668. >

I have updated "DataTypes.h.in", could you do a svn update and see if it works ? -Argiris Óscar Fuentes wrote: > Óscar Fuentes <ofv at wanadoo.es> writes: > > >>> It appears the Windows build has regressed over the past week. >>> >>> The build fails quite early (during the "Performing TableGenStep" >>> phase).

Hello I'm trying to install LLVM and LLVM GCC so I check out the source of llvm and llvm-gcc-4.2 from the svn I flow the instructions of this page http://llvm.org/docs/GCCFEBuildInstrs.html I did the installation of LLVM and LLVM GCC well but the problem is there is no llvm-gcc at the end of instalation !!! ?? I mean in the /usr/local/bin/ there are all the commands of llvm (lli llc llvmc

On Mar 29, 2010, at 6:50 AM, Kalle Raiskila wrote: > attached is a second try for the bigstack patch for SPU, with testcase. It is essentially the patch committed as 97091, and reverted as 97099, but with the following additions: > -in vararg handling, registers are marked to be live, to not confuse the register scavenger Looks good. You can try running with -verify-machineinstrs to detect