search for: llvm_obj_dir

...citonal change intended. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 171337 91177308-0d34-0410-b5e6-96231b3b80d8 But when I compile it. I still get the following link error. I don't understand why the architecture is not correct. My machine is Mac OS X 10.8.2. ~/dvcs_src/llvm_obj_dir$ ../llvm/configure ; make -j8 .... llvm[4]: Linking Debug+Asserts executable klang ld: warning: ld: warning: ignoring file /Users/py/dvcs_src/llvm_obj_dir/Debug+Asserts/lib/libLLVMX86AsmParser.a, file was built for archive which is not the architecture being linked (i386): /Users/py/dvcs_src/llvm...

...-id: https://llvm.org/svn/llvm-project/llvm/trunk at 171337 > 91177308-0d34-0410-b5e6-96231b3b80d8 > > > But when I compile it. I still get the following link error. I don't > understand why the architecture is not correct. My machine is Mac OS X > 10.8.2. > > ~/dvcs_src/llvm_obj_dir$ ../llvm/configure ; make -j8 > > .... > > llvm[4]: Linking Debug+Asserts executable klang > ld: warning: ld: warning: ignoring file > /Users/py/dvcs_src/llvm_obj_dir/Debug+Asserts/lib/libLLVMX86AsmParser.a, > file was built for archive which is not the architecture being linke...

Hello, I just applied changes of LLVM 3.2 and it is tested with LLVM 3.2 downloaded from the LLVM Download Page. I just worked for master branch only. The rest of the other branches need to be changed about this also. This will be done as soon as possible. (Before I fix this, If you look at the commits for this issue for master branch, you can easily fix it and test for others also.) Sorry for

...gether with LLVM > Project source tree. > > git://github.com/Journeyer/klang.git > > There exist many branches and each branch is for each chapter of Kaleidoscope. Hi Journeyer, Thanks! I'm following instructions in the README. But I get the following error when run make -j8 in llvm_obj_dir$. Do you know what is wrong? llvm[4]: Compiling ASTNodes.cpp for Debug+Asserts build In file included from /Users/py/dvcs_src/llvm/projects/klang/lib/AST/ASTNodes.cpp:15: /Users/py/dvcs_src/llvm_obj_dir/projects/klang/../../../llvm/projects/klang/include/klang/Driver/Driver.h:23:10: fatal error:...

Hi Sanjiv, 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > I configure llvm into a separate directory from source. > When I do the steps you mentioned in the source directory, this is what I > get. In that case, copy $LLVM_DIR/tools/llvmc/example/mcc16/Makefile to $LLVM_OBJ_DIR/tools/llvmc/example/mcc16/Makefile and build from that directory.

Hello Peng Yu and List, I have put toy.cpp into github but it has a form of LLVM project makefile infrastructure. So you can build it together with LLVM Project source tree. git://github.com/Journeyer/klang.git There exist many branches and each branch is for each chapter of Kaleidoscope. Regards Journeyer 2012/12/30 Peng Yu <pengyu.ut at gmail.com>: > Hi, > > I'm learning

...ee. >> >> git://github.com/Journeyer/klang.git >> >> There exist many branches and each branch is for each chapter of Kaleidoscope. > > Hi Journeyer, > > Thanks! I'm following instructions in the README. But I get the > following error when run make -j8 in llvm_obj_dir$. Do you know what > is wrong? > > > llvm[4]: Compiling ASTNodes.cpp for Debug+Asserts build > In file included from > /Users/py/dvcs_src/llvm/projects/klang/lib/AST/ASTNodes.cpp:15: > /Users/py/dvcs_src/llvm_obj_dir/projects/klang/../../../llvm/projects/klang/include/klang/Dri...

Hi, I'm learning the tutorial. http://llvm.org/docs/tutorial/ I'm wondering if there is already a git repository of the examples in the tutorial so that I don't have to copy the code from the webpage. Thanks! -- Regards, Peng

Mikhail Glushenkov wrote: > Hi Sanjiv, > > 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > >> Hi Mikhail, >> How do you build mcc16 executable? >> > > This should work: > > $ cd $LLVM_DIR/tools/llvmc/examples/mcc16 > $ make > > I configure llvm into a separate directory from source. When I do the steps you mentioned in

This occurs when a header file is moved or deleted. The dependency files contain the old header file and produce this error. The only way I have found to get around this is to delete all *.d files when header files are moved or deleted: % cd LLVM_OBJ_DIR % /bin/rm `find . -name '*.d'` If someone knows a better way around this,I'd love to hear it too. --Vikram -----Original Message----- From: Juan Nicolas Ruiz [mailto:juanruiz at students.uiuc.edu] Sent: Friday, November 01, 2002 12:01 PM To: Vikram S. Adve Subject: RE: CVS Broken?...

...njiv.gupta at microchip.com>: > >> I configure llvm into a separate directory from source. >> When I do the steps you mentioned in the source directory, this is what I >> get. >> > > In that case, copy $LLVM_DIR/tools/llvmc/example/mcc16/Makefile to > $LLVM_OBJ_DIR/tools/llvmc/example/mcc16/Makefile and build from that > directory. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >