From: Shane D. <sha...@ho...> - 2006-04-11 21:52:32
|
Hi Willem, Thanks for your message. I did get an error about vm.bootclasspath prior to this but it looked like it was set correctly in the config/properties files (I think I got past that one before by running from the JPF install/home dir). I tried again by adding that location to my regular classpath but got the same error. I also tried appending and prepending the location to -Xbootclasspath but there was no change (for the former) and an internal hot spot error in the latter. So maybe this is a 1.5 issue. I'll try with 1.4.2. Btw, most of this was from the cmd line but I also tried with NetBeans (and did read the page on how to set things up but still couldn't get it working from there either). Shane. >It looks to be that your vm.bootclasspath is not set correctly, since it >seems that JPF is not finding the peer classes that override some of the >Java lib classes. It should point to build/env/jpf. If you are in Eclipse >just add this folder to your classpath in the run-script. > >BTW, JPF and 1.5 is not best of friends - we will release a 1.5 compatible >version in the next week or two. To be on the safe side you might like to >use 1.4. |