Re: [Sablevm-developer] Porting SableVM to ARM: Questions

[Gunda D. <sab...@ho...>]

Etienne/Grzegorz,

Thanks for all the advice you guys gave me. I finally got everything 
compiled and ready to go.

When I ran the Hello World program, unfortunately sablevm failed. Here is 
the invocation I did

sablevm -vsgj -c "/usr/local/lib/sablevm/classes-1.0.5" Hello.class

The relevant output I got was

[verbose jni: JNI_CreateJavaVM]
[verbose gc: allocating initial heap (16777216 bytes)]
[verbose class: loading "java/lang/Object"]
sablevm: cannot create vm

What went wrong ? Any help would be appreciated.

After some testing I will post the diffs.

Thanks.
-Gunda

PS: Etienne: When you said "The fun part (let say not before January) will 
be to make the inline-threaded engine functional on ARM" what did you mean ? 
Is there something that will prevent it from working on ARM ?






>From: Grzegorz Prokopski <ga...@de...>
>To: Gunda Domlur <sab...@ho...>
>CC: SableVM-devel ML <sab...@li...>
>Subject: Re: [Sablevm-developer] Porting SableVM to ARM: Questions
>Date: 03 Dec 2002 23:59:34 +0100
>
>W li¶cie z wto, 03-12-2002, godz. 22:36, Gunda Domlur pisze:
> > Hi,
> >
> > I am trying to port sableVM for ARM linux (netwinder). After looking 
>thru
> > the archives, I already made the following changes
> >
> > system.c: iflush and compare_and_swap ported to ARM
> > system.h: The correct typedefs are in place
> > jni_system_specific.h: Necessary changes are done.
>Great!
>Could you please send the diff?
>
> > Am I missing anything else ?
>If it doesn't work by now - I can't say not looking at your changes.
>
> > Proabably a stupid question, where does the cpu type definitions (e.g.
> > __ia64__) defined ? Is it part of the configure ? Is it in the generated
> > Makefiles ? The reason is that after defining the new cpu type as 
>__arm__ I
> > get a error "unknown system" generated from the jni_system_specific.h 
>file
> > when I try to make. Is there a way to force the build to use a 
>particular
> > target type ?
>Hmm... I belive that these defines are set by build environment and we
>shouldn't need to wory about who exactly is responsible for setting
>them. The mechanism is probably a bit complicated - just imagine
>crosscompilations and the like.
>
>But getting back to your problem - AFAIK __arm__ should be defined
>while you're doing build for arm.
>
> > An early reply will be appreciated :-)
>Usually You can try to catch me at #debian-devel at irc.debian.org
>I am interested in helping you even _now_.
>
>You're welcomed
>
>				Grzegorz B. Prokopski
>
>
><< signature.asc >>


_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail