[javac] [wrote /var/tmp/portage/eclipse-sdk-3.1-r1/work/eclipse-sdk-3.1/jdtcoresrc/compiler/org/eclipse/jdt/internal/compiler/util/WeakHashSetOfCharArray.class] [javac] [total 56339ms] [echo] UPDATE ecj.jar BUILD SUCCESSFUL Total time: 1 minute 12 seconds * Bootstrapping ecj [echo] TARGET: compiler2 [echo] compilerArg -encoding ISO-8859-1 [echo] build compiler org.eclipse.jdt.core.JDTCompilerAdapter [echo] UPDATE ecj.jar BUILD SUCCESSFUL Total time: 1 minute 8 seconds * Compiling Eclipse -- see /var/tmp/portage/eclipse-sdk-3.1-r1/work/eclipse-sdk-3.1/compilelog.txt for details The JVM option is invalid: -XX:CompileThreshold=1500 Could not create the Java virtual machine. Usage: java [-options] class [args...] (to execute a class) or java [-jar] [-options] jarfile [args...] (to execute a jar file) where options include: -cp -classpath <directories and zip/jar files separated by :> set search path for application classes and resources -D<name>=<value> set a system property -verbose[:class|gc|jni] enable verbose output -version print product version -showversion print product version and continue -? -help print this help message -X print help on non-standard options -assert print help on assert options !!! ERROR: dev-util/eclipse-sdk-3.1-r1 failed. !!! Function src_compile, Line 119, Exitcode 1 !!! Failed to compile Eclipse !!! If you need support, post the topmost build error, NOT this status message. # java -version java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxppc321420-20040626 (JIT enabled: jitc)) Reproducible: Always Steps to Reproduce: 1. emerge eclipse-sdk 2. 3. Actual Results: brobken build Expected Results: eclipse build possibly, its a problem which could be solved with ibm java 1.5, but this is still in an beta-stage. Info for non-ppc-users : ibm jdk 1.4.2 is the latest, stable avaible jvm/jdk for the ppc with linux. there is no sun jdk/jvm for linux on the ppc still existent. So, a hint like "use sun java x.x or x " has no relevance. Cheers Frank
Are you still experiencing this problem? It is also worth noting that 3.1.1 is now in portage.
No, its gone- the new version of Java from IBM fixed it, I guess.
Re-opening to marked fix...
Marking fixed.