Re: Building kissme with classpath 0.04

[Alex Lau]

John Leuner :

> Hello Alex
>
> I'm sorry for responding so late.
>
> If you want to build Classpath 0.04 and kissme you must do the following:
>
> 1. Unpack and build classpath
>
>   ./configure --enable-jni --with-jikes
>   make
>   make install
>  
this work ok. I'm not sure I understand the concept ... so the VM build 
after
the classpath? I always throught classpath should build after the VM is in
place....

> 2. Get kissme from CVS 
>
>   (and also) 
>   mkdir kissme-classpath
>   touch kissme-classpath/somefile
>   
that I'm not sure I do it right... should kissme-classpath inside of 
classpath dir?
or it doesn't matter? touch ... should I run "make clean" to make sure?

> 3. build kissme:
> 	  
>    aclocal
>    automake -a
>    autoconf
>    ./configure --with-gnu-classpath=/somedir/classpath-0.04     
>    make
>  
didn't know is the version of my automake and autoconfig not right or
what .... it just doesn't like it..
/kissme/vm/garbage.c(.data+0x0): multiple definition of 
`GARBAGE_INITIALHANDLENUM
the rest I understand.
and in the configure of kissme should I also use --with-mauve also?
Alex

> 3.5 build kissme .classes files:
>
>    jikes -classpath /usr/share/classpath/glibj.zip:classes `find classes/{java,gnu,plava,jos} -name '*.java'`   
>
> 4. Set your LD_LIBRARY_PATH:
>
>   export LD_LIBRARY_PATH=/usr/lib/classpath
>
> 5. run kissme
>   ./kissme -classpath classes:/usr/share/classpath/glibj.zip:. myclass
>
>
> Feel free to ask me any questions about kissme or classpath or mauve.
>
> John Leuner
>
>  
>
> > Sorry haven't join the kissme mailing list yet.. but I will. Since you
> > are build kissme and get deb for it. I think I'm try to port the test
> > base on kissme first ( classpath did suggest which vm I should use )
> > Questions :)
> > 1) I don't know you see my testio.sh file in the classpath list
> > earier, it run under your kissme deb (sid). But when I build the cvs
> > classpath by hand, it keep giveing me seg fault, Question is do I
> > need to build the kissme bin also? will the kissme-classpath and kissme
> > source (deb source ) good enought for mauve test building ground?
> >
> > 2) when the classpath is build, doesn't require the vm hook in the src to
> > finish build or it can user share lib?  my picture is not very clear here
> >
> > java ----> JDK spec ---> classpath API ---> native code ---> lib ? (not 
> > good)
> >                                                       ---> vm---> lib 
> > ? (better)
> > is that right? please correct me.
> >
> > 3) if I understand correctly, each "out of box" ( as include classpath 
> > and vm )
> > will need to be build differently? (correct me )
> >    
>
>
> _______________________________________________
> Classpath mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/classpath
>