similar to: [LLVMdev] [vmkit] Cross-compilation

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 Harris, A question has arisen, what is the difference between VMKit2 and VMKit, and why, in the first place the new VMKit2 fork was been created? Thanks for answer :) Best regards, Minas On Tue, Feb 12, 2013 at 2:36 PM, Harris Bakiras <h.bakiras at gmail.com> wrote: > Hi Chris, > > For the moment you can install VMKit following these instructions: > >

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 Minas, Basically, you should not have any difference between the two projects :) (it's not really the case, but we are working on this problem). To explain (sorry for my long email!), I work for a french research institution (Inria) and, as we have an Inria research project around VMKit, I had to create a repository inside my institution (a researcher has always to make his institution

on 2013/3/1 6:11, Gaël Thomas wrote: > > Fundamentally, I think that for the VMKit project, it's important to > be hosted as a subproject of llvm because VMKit heavily relies on llvm > (and because llvm is maybe a little bit more attractive than inria:)). > So, we will quickly re-merge the two projects and continuously > integrates the stable (and interesting) contributions

OK, figured out that to cross-compile LLVM for another target I need to ./configure with --build=<build system triple> --host=<target system triple>. This works fine for llvm, clang and even (apparently) classpath but when I try to do the same for vmkit2 it fails with "checking for ../../classpath-0.99/<build-dir>/lib/... configure: error: cannot check for file existence

Hi Julien, Due to some new commits, openjdk build is broken for the moment. We are fixing this. You can temporarily use the following commit to try VMKit with OpenJDK implementation. d9bf3794d66a116999f8f16d0799fba6fe5bd822 just call the following command in your vmkit directory: git checkout d9bf3794d66a116999f8f16d0799fba6fe5bd822 Harris Bakiras On 03/18/2013 10:12 AM, Julien Pagès

Hi, I see that now vmkit2 contains the last revisions of the project, so I follow these instructions to compile vmkit : http://vmkit2.gforge.inria.fr/start.php I download and compile LLVM without errors. I have tested with and without optimizations but this is the same for the errors. My configuration for LLVM is just : ./configure; make Apparently we can build vmkit with OpenJDK instead of GNU

Hi all, After "BUILD SUCCESSFUL" Message on compiling VMkit. The make starts compiling mmtk-vmkit.jar The following command errors out: Compiling 'mmtk-vmkit.jar' /vmkit/Release+Asserts/bin/vmjc -load=/vmkit/Release+Asserts/lib/MMTKRuntime.so -load=/vmkit/Release+Asserts/lib/MMTKMagic.so -LowerMagic /vmkit/mmtk/java/Release+Asserts/mmtk-vmkit.jar -disable-exceptions

Hi all, After "BUILD SUCCESSFUL" Message on compiling VMkit. after the make starts compiling mmtk-vmkit.jar In verbose mode the following command errors out: /home/usr/vmkit/Release+Asserts/bin/vmjc -load=/home/usr/vmkit/Release+Asserts/lib/MMTKRuntime.so -load=/home/usr/vmkit/Release+Asserts/lib/MMTKMagic.so -LowerMagic /home/usr/vmkit/mmtk/java/Release+Asserts/mmtk-vmkit.jar

Are you running on 64bit (your backtrace addresses suggest you are)? I'm encountering the same error when trying to use VMKit on 64bit, which I believe is an unsupported target. ~Will On Tue, Aug 23, 2011 at 5:17 PM, Frederic Perez Ordeig <fredericp at gmail.com> wrote: > I'm trying to build the SVN version of VMKit and I'm getting this error > while building. > I

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 > > //

Hi Frederic, On Wed, Aug 24, 2011 at 11:01 AM, Frederic Perez Ordeig <fredericp at gmail.com > wrote: > Ah yes, thanks, this was one problem, now I hit another: > > llvm[2]: Building Release+Asserts mmtk-vmkit.jar all > Thread 0x110000000 received a SIGSEGV: either the VM code or an external > native method is bogus. Aborting... > ; 0x5cfeed (0x1100fe410) in

I'm trying to build the SVN version of VMKit and I'm getting this error while building. I have llvm and clang built from SVN too. Any help? llvm[2]: Building Release+Asserts mmtk-vmkit.jar all vmjc: JavaClass.cpp:442: j3::JavaObject *j3::Class::doNew(j3::Jnjvm *): Assertion `this && "No class when allocating."' failed. 0 vmjc 0x0000000000e9c44f 1 vmjc

Ah yes, thanks, this was one problem, now I hit another: llvm[2]: Building Release+Asserts mmtk-vmkit.jar all Thread 0x110000000 received a SIGSEGV: either the VM code or an external native method is bogus. Aborting... ; 0x5cfeed (0x1100fe410) in _Z14sigsegvHandleriP7siginfoPv ; 0x2b889c232c60 in Unknown method ; 0x561499 (0x1100fe900) in _ZN2j310JavaObject7acquireEPS0_ ; 0x55b464 (0x1100fe920)

Hi Joshua, > $ j3 Hello > j3: JavaClass.cpp:480: j3::JavaObject* j3::Class::doNew(j3::Jnjvm*): > Assertion `(this->isInitializing() || > classLoader->getCompiler()->isStaticCompiling()) && "Uninitialized class > when allocating."' failed. > Aborted Regarding to j3 in 64 bit version, it should work now after we've found crush reason, both in

Hi Sergii, I think there is a problem in your configure command for VMKit. If you look at what you provide for glibj: --with-gnu-classpath-glibj="/home/svozniuk/llvm/classpath-0.97.2 I don't think it's right. You should change it to: --with-gnu-classpath-glibj="/home/svozniuk/llvm/classpath-0.97.2/lib/glibj.zip Also please make sure that you have created the links for the

Hi Yi, The precompiler is in charge of translating the most common classes of the Java runtime library to llvm code (typically, java.lang.Object), in order to natively compile these classes and decrease the bootstrap time. So, if you have a segmentation fault at this stage, it means that you have broken something in the interface between MMTk and VMKit. If it can helps you: * during a first

Hmm, disregard my previous comment (while you might still have issues with 64bit, that's not what's primarily causing your issue)--your particular error is when you don't point vmkit to the classpath libraries properly. Set it with the configure option --with-gnu-classpath-glibj=/path/to/classpath-0.97.2/lib/glibj.zip Good luck! ~Will On Tue, Aug 23, 2011 at 5:49 PM, Will Dietz

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