similar to: [LLVMdev] [patch] VMKIT: change in header file paths

Thanks Favios for finding the problem! I have applied a patch to Makefile.rules, hopefully it now works without you editing some files. About VMKIT_SRC_ROOT and PROJ_SRC_ROOT, it is fine to have both in the code. I find it clearer to use VMKIT_SRC_ROOT. Nicolas On Sun, Jun 10, 2012 at 10:09 PM, Foivos S. Zakkak <foivos at zakkak.net>wrote: > Hi Nicolas, > > I finally found the

Hi Fovios, Do you have a ./lib/j3/LLVMRuntime/LLVMRuntime.inc file being generated? What does it contain? Nicolas On Thu, Jun 7, 2012 at 5:47 PM, Foivos S. Zakkak <foivos at zakkak.net> wrote: > Still the same. > > Is there any chance that the placement of my directories are causing this? > > Also the exact command that fails is > >

Hi Nicolas, I finally found the root of the problem. Build was unable to locate llvm-build because it was looking for it in path/to/vmkit_src/utils/llvm-build while it was located in path/to/llvm_src/utils/llvm-build Actually llvm-build's path is defined by the path/to/llvm_src/Makefile.rules and looks like this LLVMBuildTool := $(PROJ_SRC_ROOT)/utils/llvm-build/llvm-build however in

Hi Nicolas, it looks like there are missing things $ more lib/j3/LLVMRuntime/LLVMRuntime.inc // Generated by llvm2cpp - DO NOT MODIFY! Module* makeLLVMModuleContents(Module *mod) { mod->setModuleIdentifier("<stdin>"); // Type Definitions // Function Declarations // Global Variable Declarations // Constant Definitions // Global Variable Definitions // Function

On Jun 7, 2012, at 4:32 PM, Foivos S. Zakkak wrote: > Hi Nicolas, > > it looks like there are missing things > > $ more lib/j3/LLVMRuntime/LLVMRuntime.inc > // Generated by llvm2cpp - DO NOT MODIFY! > > > Module* makeLLVMModuleContents(Module *mod) { > > mod->setModuleIdentifier("<stdin>"); > > // Type Definitions > > //

Still the same. Is there any chance that the placement of my directories are causing this? Also the exact command that fails is /home1/public/zakkak/java/vmkit/Release+Asserts/bin/vmjc -std-compile-opts -load=/home1/public/zakkak/java/vmkit/Release+Asserts/lib/MMTKRuntime.so -load=/home1/public/zakkak/java/vmkit/Release+Asserts/lib/MMTKMagic.so -LowerMagic

On Thu, Jun 7, 2012 at 4:27 PM, Foivos S. Zakkak <foivos at zakkak.net> wrote: > Hi Nicolas, > > I thought MMTk is written in java and it is compiled by javac. > It is compiled by javac to produce Java bytecode. Then vmkit runs the initialization code of MMTk (through the JIT) and generates the binary code through llvm. > retried a clean build with JIT enabled > >

Hi Fovios, On Thu, Jun 7, 2012 at 3:51 PM, Foivos <fivosz at gmail.com> wrote: > Hi, > > My machine is running Ubuntu server 64-bit > And the revision from the trunk is 158095 for llvm, clang and vmkit > > llvm configuration > ../../llvm/configure --enable-doxygen --enable-optimized --disable-jit > Why do you disable the JIT? VMKit needs it to compile MMTk.

Hi Nicolas, I thought MMTk is written in java and it is compiled by javac. retried a clean build with JIT enabled llvm configuration ../../llvm/configure --enable-doxygen --enable-optimized --enable-jit vmkit configuration ../../llvm/vmkit/configure --with-llvmsrc=/home1/public/zakkak/llvm/ --with-llvmobj=/home1/public/zakkak/java/llvm/

Hi, My machine is running Ubuntu server 64-bit And the revision from the trunk is 158095 for llvm, clang and vmkit llvm configuration ../../llvm/configure --enable-doxygen --enable-optimized --disable-jit vmkit configuration ../../llvm/vmkit/configure --with-llvmsrc=/home1/public/zakkak/llvm/ --with-llvmobj=/home1/public/zakkak/java/llvm/

Hello, after completing the build i get ... BUILD SUCCESSFUL Total time: 5 seconds llvm[2]: Building Release+Asserts mmtk-vmkit.jar all vmjc: /home1/public/zakkak/llvm/lib/VMCore/Type.cpp:747: static llvm::PointerType *llvm::PointerType::get(llvm::Type *, unsigned int): Assertion `EltTy && "Can't get a pointer to <null> type!"' failed. 0 vmjc

Hi Fivos, I cannot reproduce on my machine (ubuntu 64bit, clang/llvm/vmkit on svn trunk). What's your configuration? Cheers, Nicolas On Tue, Jun 5, 2012 at 3:08 PM, Fivos <fivosz at gmail.com> wrote: > Hello, > > after completing the build i get > > ... > BUILD SUCCESSFUL > Total time: 5 seconds > llvm[2]: Building Release+Asserts mmtk-vmkit.jar all > vmjc:

Hi Chris, For the moment you can install VMKit following these instructions: http://vmkit2.gforge.inria.fr/start.php VMKit's web page and repository will be updated soon. Harris Bakiras Le 12/02/2013 10:30, chris.gray at kiffer.be a écrit : > Hi all, > > I hope this is the correct place to post such questions? I am building > vmkit for the first time, following the

Hi all, I am trying to build VMKit on Linux/x86 and I got error messages like below, llvm[1]: Linking Debug+Asserts executable vmjc /root/llvm/vmkit/tools/vmjc/Debug+Asserts/vmjc.o: In function `mvm::SpinLock::acquire()': /root/llvm/vmkit/include/mvm/Threads/Locks.h:164: undefined reference to `__sync_val_compare_and_swap_4' /root/llvm/vmkit/include/mvm/Threads/Locks.h:168: undefined

Hi all, I hope this is the correct place to post such questions? I am building vmkit for the first time, following the instructions on the get_started page (with one deviation: in step 4 I ran ./configure in my vmkit directory and therefore did not need to cd at the start of step 5. Is this correct?). Build platform is 64-bit CrunchBang Linux 11 "Waldorf", based on Debian Wheezy. I

Hi Nicolas, I found a 32bit Lucid machine (but it'd be great if there was a working 64bit version though). Everything was checked out this morning. I now am able to build vmkit with this configuration: ./configure --with-llvmsrc=/home/zoewolk/RESEARCH/llvm --with-llvmobj=/home/zoewolk/RESEARCH/llvm --with-gnu-classpath-glibj=/home/zoewolk/RESEARCH/classpath-0.97.2/lib

Hi Nicolas, thanks, it works fine :) Is there any manual/documentation available for vmkit? Do you know if there is an easy way to completely disable JIT and interpret the code instead? Foivos On 06/11/2012 04:51 PM, Nicolas Geoffray wrote: > Thanks Favios for finding the problem! I have applied a patch to > Makefile.rules, hopefully it now works without you editing some files. >

While building i got this error Error: JAVA_HOME is not defined correctly. I wonder why vmkit requires JAVA_HOME, i would expect it to be independent of any java staff except the classspath. Am i missing something? Thank you Foivos

While building i got this error Error: JAVA_HOME is not defined correctly. I wonder why vmkit requires JAVA_HOME, i would expect it to be independent of any java staff except the classspath. Am i missing something? Thank you Foivos

Hello, As i understand vmkit's Makefiles are not written to support cross compilation. It looks like they ignore the --target flag from the configuration. Please correct if i am wrong. I would like to make a request to add cross compilation support to the project. I am willing to contribute if needed Thank you Foivos