search for: bytecode_librari

Hi, I compiled LLVM with debug symbols as: ./configure --enable-profiling --enable-assertions --enable-expensive-checks --enable-debug-runtime --enable-debug-symbols make ENABLE_OPTIMIZED=0 But now if I use 'BYTECODE_LIBRARY=1' in my llvm pass Makefile then I get the following warning: /data/ahmad/llvm/llvm31/Makefile.rules:1273: Bytecode libraries require LLVM capable compiler but none

On 9/29/11 11:23 AM, Eric Christopher wrote: > On Sep 29, 2011, at 12:53 AM, Speziale Ettore wrote: > >> Hi, >> >>> What compiler are you using to build with? I've made it default to clang with less looking around for llvm-gcc, so there may be an issue there. What is your configure line? What host are you trying to build on? >> First I have compiled llvm/clang

On 9/29/11 11:45 AM, Eric Christopher wrote: >> (I'm jumping into the middle of this conversation as it looks like you're discussing something that might be relevant to my work. Sorry I'm not up to speed on the full context of the discussion...) >> >> If you are asking whether anyone is using machinery in LLVM's build system to compile programs into LLVM bitcode

>> > > (I'm jumping into the middle of this conversation as it looks like you're discussing something that might be relevant to my work. Sorry I'm not up to speed on the full context of the discussion...) > > If you are asking whether anyone is using machinery in LLVM's build system to compile programs into LLVM bitcode files, the answer is yes. The LLVM

On Sep 29, 2011, at 10:35 AM, John Criswell wrote: > On 9/29/11 11:45 AM, Eric Christopher wrote: >>> (I'm jumping into the middle of this conversation as it looks like you're discussing something that might be relevant to my work. Sorry I'm not up to speed on the full context of the discussion...) >>> >>> If you are asking whether anyone is using

On 9/29/11 12:39 PM, Eric Christopher wrote: > On Sep 29, 2011, at 10:35 AM, John Criswell wrote: > >> On 9/29/11 11:45 AM, Eric Christopher wrote: >>>> (I'm jumping into the middle of this conversation as it looks like you're discussing something that might be relevant to my work. Sorry I'm not up to speed on the full context of the discussion...)

On Sep 29, 2011, at 12:53 AM, Speziale Ettore wrote: > Hi, > >> What compiler are you using to build with? I've made it default to clang with less looking around for llvm-gcc, so there may be an issue there. What is your configure line? What host are you trying to build on? > > First I have compiled llvm/clang compiled with "gcc (Gentoo 4.5.2 p1.1, > pie-0.4.5)

Hi, > What compiler are you using to build with? I've made it default to clang with less looking around for llvm-gcc, so there may be an issue there. What is your configure line? What host are you trying to build on? First I have compiled llvm/clang compiled with "gcc (Gentoo 4.5.2 p1.1, pie-0.4.5) 4.5.2". Then I have installed llvm/clang. They are in the path: $ clang

If you're on the new Makefile system, you will want to update your Makefile.rules. The patch below provides some important fixes for parallel builds and dependencies. It also adds some new features like the -local targets. For example, you can now build "all-local" to build the local directory without recursing into subdirectories. See the comments below for details of the change.

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron