similar to: [LLVMdev] linkage failure

Building llvm is failing for me today. I am using clang++ to build (which has not changed). llvm[2]: Compiling EDMain.cpp for Debug+Asserts build (PIC) EDMain.cpp:267:39: error: C-style cast from '::EDTokenVisitor_t' (aka 'int (^)(EDTokenRef)') to 'llvm::EDTokenVisitor_t' (aka 'int (^) (llvm::EDToken *)') is not allowed return

On Jul 22, 2010, at 8:57 AM, Fariborz Jahanian wrote: > > Building llvm is failing for me today. I am using clang++ to build > (which has not changed). > > llvm[2]: Compiling EDMain.cpp for Debug+Asserts build (PIC) > EDMain.cpp:267:39: error: C-style cast from '::EDTokenVisitor_t' (aka > 'int (^)(EDTokenRef)') to 'llvm::EDTokenVisitor_t' (aka

On Jul 22, 2010, at 2:53 PM, Eric Christopher wrote: > > On Jul 22, 2010, at 8:57 AM, Fariborz Jahanian wrote: > >> >> Building llvm is failing for me today. I am using clang++ to build >> (which has not changed). >> >> llvm[2]: Compiling EDMain.cpp for Debug+Asserts build (PIC) >> EDMain.cpp:267:39: error: C-style cast from

Hi Samuel, I always just click the icon for CMake on the Mac. Then you select a destination directory for the headers from the graphical user interface and the source where the cmakefile.txt root is. Then you click on the configure button at the bottom. It will ask you if you want to make Unix Makefiles or XCode Projects or Eclipse Projects or a couple of other options. Pick the one you

Hello, I am building LLVM with ninja on Linux environment and I continue to have the error below. I am thinking that the cause might be my PC not having sufficient RAM memory. In this sense, I extended my swap memory with a swap file (90GB), but it didn't solved the problem. Should I add more physical RAM memory to my PC, or is there any software based solution I can try first? Thank you and

On Sat, Jun 5, 2010 at 3:18 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Tom, > > I'm pretty sure that the LLVMContext constructor is defined in libLLVMCore.a > What is the output of `llvm-config --libs bitwriter`?  Does it include > -lLLVMCore? Hi Duncan, e0082888 at e0082888-laptop:~$ local/bin/llvm-config --libs bitwriter -lLLVMBitWriter -lLLVMCore -lLLVMSupport

Hi Oscar, I tried that but it didn't work. However, it did work fine on Linux for me so I am now a bit confused. Here is the output from $ sudo make install Install the project... -- Install configuration: "Release" -- Installing: /usr/local/llvm-2.8/lib/libLLVMSupport.a -- Installing: /usr/local/llvm-2.8/lib/libLLVMSystem.a -- Installing: /usr/local/llvm-2.8/lib/libLLVMCore.a --

We were successful in upgrading our JIT project to LLVM 3.0rc4 last week, after initially struggling with the various usage and IR changes from V2.9. But we have some follow-up questions: 1) In spite of building and running our tests cleanly with DEBUG+ASSERTS and RELEASE builds, we consistently see a crash when we use a DEBUG build without ASSERTs. The crash appears whenever we use the

Hey, So in Fedora rawhide we are now building llvm 3.7.1 into the lots of little shared libraries format. However I'm running into a major problem with the fact that sometimes dlclose isn't dropping all the LLVM libraries from the address space of the process. We have a sequence like this: a) X server asks mesa gbm library to init, it loads the kms_swrast_dri.so with

Hello, After I try making a clean build and got the following error: llvm[3]: Compiling EDDisassembler.cpp for Release build In file included from /llvm/include/llvm/Target/TargetSelect.h:38, from /llvm/lib/MC/MCDisassembler/EDDisassembler.cpp:37: /llvm/stage1/include/llvm/Config/AsmPrinters.def: In function ‘void LLVMInitializeX86TargetAsmPrinter()’:

Hi Jean-Daniel, My fault, I'm sure, but I don't see the problem yet. Is it possible your version of llvm/Config/AsmPrinters.def has X86 listed twice? - Daniel On Mon, Aug 2, 2010 at 12:43 AM, Jean-Daniel Dupas <devlists at shadowlab.org> wrote: > Hello, > > After I try making a clean build and got the following error: > > llvm[3]: Compiling EDDisassembler.cpp for

I fixed all the other build errors. This is the only one pending. On Tue, Jun 5, 2012 at 8:33 PM, AbhishekR <abhishekr1982 at gmail.com> wrote: > I fixed most of the errors. > > There is a weird error I am seeing and seems to be some incompatibility in > expanding macros between FileSystem.h in LLVM and intl.h in wxWidgets. Any > idea how to fix this? > > In file

Hi, In another post I was trying to find out how to use libc++ instead of libstdc++ when compiling llvm/clang. I couldnt find the a way to tell cmake to do that. So I switched to using configure to compile llvm/clang. But now I find that the artifacts produced are different. Here are the issues I see: - configure doesnt seem to respect '--prefix' option, it just puts

I fixed most of the errors. There is a weird error I am seeing and seems to be some incompatibility in expanding macros between FileSystem.h in LLVM and intl.h in wxWidgets. Any idea how to fix this? In file included from /home/arhishee/work/llvm-tv/llvm-tv/tools/llvm-tv/GraphDrawer.cpp:4: In file included from /home/arhishee/work/llvm-tv/llvm30/include/llvm/Support/FileUtilities.h:18: In file

I'm trying to do a simple build from the git 8.0.0 sources. The sources seem to build OK but a link step fails from running out of memory. I need some clues how to figure out where the bottleneck might be. The cmake command is: cmake -G Ninja                                          \     -DLLVM_TARGETS_TO_BUILD=X86                         \    

Hi, I just checked out llvm from svn and attempted to build the systemz + cpp targets. I am getting the following error: EDDisassembler.cpp:42:49: error: ../../lib/Target/X86/X86GenEDInfo.inc: No such file or directory Is that file which is generated as part of the build process? If so, I assume EDDisassembler shouldn't be compiled for a systemz build. Neale -------------- next part

The following configure/make is failing on the top of tree llvm/clang sources: ./configure --enable-optimized --disable-assertions --enable-targets=x86,x86_64,arm --build=x86_64-apple-darwin10 ./make clang-only llvm[2]: Compiling Tool.cpp for Release build In file included from /Volumes/work/gclayton/Documents/src/llvm/include/llvm/Target/TargetSelect.h:38, from

Hi Daniel, attached is a patch that pushes most of the object file specific parsing out of AsmParser and down into MachOAsmParser. This was done as a cleanup for the ELF work. I know that you're not happy with this approach, particularly the fact that as we add more object file formats and assembler dialects, it's going to cause a class explosion. But I was hoping that we could use this

On 09/02/2011 05:58 PM, Duncan Sands wrote: > Hi Yiannis, > >> I have been using llvm 2.8 (i know ancient history!) for a backend that i was >> implementing. I have been trying to port my patches to latest llvm (svn build) >> lately but i have one problem as far as the Exception Handling mechanism is >> concerned. It seems that there are no Exception Tables generated

In response to: > Date: Wed, 23 Nov 2011 18:24:16 +0100 > From: Duncan Sands <baldrick at free.fr<mailto:baldrick at free.fr>> > Subject: Re: [LLVMdev] Follow-up questions after successful upgrade to > LLVM 3.0rc4 > To: llvmdev at cs.uiuc.edu<mailto:llvmdev at cs.uiuc.edu> > Hi Kevin, >> Since I don't have llvm-gcc installed, I tried to do the