From: Ian R. <ian...@ma...> - 2007-10-31 10:10:13
|
Hi Yan, Yan Tang wrote: > Hi All, > > I am still struggling with running eclipse on jikesrvm. > > I tried many different config versions: > > Jikesrvm eclipse > 2.4.2 3.1.2 directly died > 2.4.2 3.1.0 directly died > 2.4.1 3.1.2 directly died > 2.4.1 3.1.0 directly died > 2.4.6 3.1.0 can only see "launching > workspace window" > 2.4.6 3.1.2 can only see "launching > workspace window" > > All of them are failed. > There are loads of issues with all the old RVMs, really you should be looking to run with 2.9.2 or the SVN head. > I really want to know is there anyone tried to run eclipse 3.1.* on 2.4.* ? > I ran 3.2 on 2.4.5 or 2.4.6 iirc. Remember that AWT was fundamentally broken for a long time in the 2.4 releases. I ran eclipse when I fixed the AWT peers and stuck a screen shot on my website. > All of them failed at here: > > // this is the address of the malloc'ed JavaVM struct (one per VM) > private static Address JavaVM; > > private static native Address createJavaVM(); > > private static int GetJavaVM(VM_JNIEnvironment env, Address StarStarJavaVM) { > if (traceJNI) VM.sysWrite("JNI called: GetJavaVM \n"); > > if (JavaVM == null) { > JavaVM = createJavaVM(); <---- failed here, unimplemented method > } > > if (traceJNI) VM.sysWriteln(StarStarJavaVM); > StarStarJavaVM.store(JavaVM); > > return 0; > } > > I think it is because creatJavaVM() this function is a jni function, > and it is not implemented in Jikesrvm 2.4.2 . > > I read the user guide of jikesrvm, it said something like: > > Directly-Exported Invocation Interface Functions These functions > (GetDefaultJavaVMInitArgs, > JNI CreateJavaVM, and JNI GetCreatedJavaVMs) are not implemented. > This is because we > do not provide a virtual machine library that can be linked > against, nor do we support native > applications that launch and use an embedded Java VM. There is no > inherent reason why > this could not be done, but we have not done so yet. > > Note that it said "JNI CreateJavaVM is not implemented", I guess this > is the reason. > > HOWEVER, i know at least two or three guys posted msg before in the newsgroup > said they can run eclipse 3.1 with jikesrvm 2.4.2 . > > I am really frustrated with this error, ;-( > So I don't really want to try a really, really, really.... old version of the RVM and a really old version of eclipse. But I tried running eclipse 3.2 on the RVM without success. So I created a JIRA tracker: http://jira.codehaus.org/browse/RVM-332 It did, however, run eclipse for a short while before failing :-) Regards, Ian |