You can disable the warnings. Look at the classlib build. We should clean them up when appropriate though.
-Nathan On 3/9/07, Gregory Shimansky <[EMAIL PROTECTED]> wrote:
Vladimir Ivanov wrote: > Issue 3348 was created to track it. > thanks, Vladimir I've tried the patch in it. It seems to work, so I'll commit it if tests pass. Eclipse compiler also finds tons of warnings in kernel classes. It would be good to fix them too. > On 3/9/07, Vladimir Ivanov <[EMAIL PROTECTED]> wrote: >> OK, in this case we should use compiler defined in the >> classlib/properties.xml. >> I'll prepare patch. >> Thanks, Vladimir >> >> On 3/9/07, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: >> > >> > On Mar 9, 2007, at 6:39 AM, Vladimir Ivanov wrote: >> > >> > > Hello everybody, >> > > I try to build the HDK by HDK. Now it failed to build DRLVM with >> > > message: >> > > trunk/working_vm/build/lnx_em64t_gcc_release/semis/build/targets/ >> > > build.java.xml:10: >> > > Unable to find a javac compiler; >> > > com.sun.tools.javac.Main is not on the classpath. >> > > Perhaps JAVA_HOME does not point to the JDK >> > > Total time: 8 minutes 36 seconds >> > > >> > > Seems we need to define java compiler for DRLVM somewhere in the >> > > property files. Which one is correct? I see some property files in >> the >> > > DRLVM instead of one in the CLASSLIB: drlvm.properties (optional), >> > > lnx.properties, win.properties, harmonyvm.properties and >> > > test.properties. Also we can use CLASSLIB properties.xml. Which >> one is >> > > correct? >> > > >> > > Now I update lnx.properties file locally to define other possible >> > > issues. >> > >> > I think the right thing to do is switch to the eclipse compiler, >> > since we require that to build the class library. yea? nea? >> > >> > geir >> > >> > >> > -- Gregory
