* Creating the Class Data Sharing archives Error occurred during initialization of VM Dumping a shared archive is not supported on the Server JVM. I know that ia64 is currently not supported - but do you know a workaround for this issue? Are these archives strictly necessary? Reproducible: Always
Created attachment 345232 [details] emerge --info
Created attachment 345234 [details] build.log
Fixed in sun-jdk-1.6.0.45. Thanks for the report.
Actually, emerging sun-jdk-1.6.0.45 (as well as sun-jre-1.6.0.45) still fails as ebuild still has incorrect statement for ia64: # see bug #207282 einfo "Creating the Class Data Sharing archives" case ${ARCH} in ia64) bin/java -client -Xshare:dump || die ;; x86) bin/java -client -Xshare:dump || die # limit heap size for large memory on x86 #405239 # this is a workaround and shouldn't be needed. bin/java -server -Xmx64m -Xshare:dump || die ;; *) bin/java -server -Xshare:dump || die ;; esac BTW, ia64 is not the only affected architecture. From [1], -Xshare option is only supported on 32-bit JVMs. So fallback case may be problematic for some. Furthermore, I can't find a -client option for, at least, ia64. dev-java/oracle-jdk-bin and dev-java/oracle-jre-bin also have this erroneous statement, although ia64 isn't supported, so could be removed from the architecture case there. [1] http://docs.oracle.com/javase/6/docs/technotes/guides/vm/class-data-sharing.html
I confirm that this issue still persists. In addition and unrelated, the checksum for the .bin file is wrong.
(In reply to Dennis Schridde from comment #5) > In addition and unrelated, the checksum for the .bin file is wrong. Furthermore, sun-jcontrol.png and the associated .desktop file does not exist here.
Updated bug summary to reflect the packages we should still deal with; we no longer deal with sun-jdk and sun-jre-bin as they are masked, therefore unsupported and are bound to be removed at some point in the future.
(In reply to Tom Wijsman (TomWij) from comment #7) > Updated bug summary to reflect the packages we should still deal with; we no > longer deal with sun-jdk and sun-jre-bin as they are masked, therefore > unsupported and are bound to be removed at some point in the future. dev-java/oracle-jdk-bin does not support ia64. And if you remove sun-jdk, you also remove Java for ia64, as that is the last and only JDK that reliably works there - dev-java/icedtea[zero] was removed long ago, and it was never able to properly run all Java code.
(In reply to Dennis Schridde from comment #8) > dev-java/oracle-jdk-bin does not support ia64. And if you remove sun-jdk, > you also remove Java for ia64, as that is the last and only JDK that > reliably works there - dev-java/icedtea[zero] was removed long ago, and it > was never able to properly run all Java code. Thank you for those details, seems we need to keep things around longer for them.
(In reply to Émeric Maschino from comment #4) > Actually, emerging sun-jdk-1.6.0.45 (as well as sun-jre-1.6.0.45) still > fails as ebuild still has incorrect statement for ia64: > > # see bug #207282 > einfo "Creating the Class Data Sharing archives" > case ${ARCH} in > ia64) > bin/java -client -Xshare:dump || die > ;; > x86) > bin/java -client -Xshare:dump || die > # limit heap size for large memory on x86 #405239 > # this is a workaround and shouldn't be needed. > bin/java -server -Xmx64m -Xshare:dump || die > ;; > *) > bin/java -server -Xshare:dump || die > ;; > esac > > BTW, ia64 is not the only affected architecture. From [1], -Xshare option is > only supported on 32-bit JVMs. So fallback case may be problematic for some. > Furthermore, I can't find a -client option for, at least, ia64. > > dev-java/oracle-jdk-bin and dev-java/oracle-jre-bin also have this erroneous > statement, although ia64 isn't supported, so could be removed from the > architecture case there. > > [1] > http://docs.oracle.com/javase/6/docs/technotes/guides/vm/class-data-sharing. > html x86_64 supports CDS and the statement is about using when the official Sun 32-bit installer. x86_32 has two jvms, one named client the other server. Only the server jvm was ported to x86_64. CDS should be generated for each installed jvm. For jdk/jre packages having only one jvm a plain "java -Xshare:dump" would actually do.
> dev-java/oracle-jdk-bin does not support ia64. And if you remove sun-jdk, > you also remove Java for ia64, as that is the last and only JDK that > reliably works there - dev-java/icedtea[zero] was removed long ago, and it > was never able to properly run all Java code. Currently icedtea uses jamvm as JVM on ia64, quite a bit faster then zero x86 and much more stable than zero. You might want to give it a try.
We just dropped java on ia64 so closing.
