|Summary:||java / jvmsetup doesn't work|
|Product:||[Retired] Red Hat Linux||Reporter:||Mikael Carneholm <carniz>|
|Component:||openoffice.org||Assignee:||Dan Williams <dcbw>|
|Status:||CLOSED WONTFIX||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2003-12-05 20:31:00 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Mikael Carneholm 2003-03-10 13:00:43 UTC
Description of problem: Running /usr/lib/openoffice/program/jvmsetup yields "Java cannot be configured" Version-Release number of selected component (if applicable): 1.0.2 How reproducible: Always. Steps to Reproduce: 1. From a terminal, run /usr/lib/openoffice/program/jvmsetup Actual results: "Java cannot be configured" Expected results: The program should start and let me configure which jvm to use (I suppose) Additional info: As OOo is "pre-installed" and pre-configured in phoebe, the installation program that normally detects what jvm to use will never be run and java will thus be hard to setup without the help of jvmsetup. If a jvm was shipped with RH and OOo was pre-configured to use this jvm this would not be an issue, but as long as this is not the case you will have to install java post installing OOo and there should thus be an easy way to make java work with OOo.
Comment 1 Nahum Castro 2003-07-10 06:17:12 UTC
Created attachment 92858 [details] not works On RedHat 8.0 the same problem exist, once a RedHat Engineer told me that they not shipped Java so the jvmsetup will not work, but jvmsetup is just a file with the next: #/bin/sh echo Java cannot be configured So they (redhat) disabled or changed jvmsetup with a purpose unknow to me. If you try to install OOo downloaded from www.openoffice.org the suite will not work at all (crashes on startup). So the best solution to me is downgrade to RH 7.3 or change to Mandrake 9.1.
Comment 2 Dan Williams 2003-12-05 20:31:00 UTC
Correct, Java is not enabled for the builds because we do not ship Java with OOo. We won't ship an SRPM that cannot be built on the base system, that's just bad form. However, with 1.1.0 I've added simple switch to flip in the specfile, plus you point the specfile to your JDK, and thats it to get your build with Java. We are working on getting OOo to compile the Java bits iwth GCJ, and when that is successful, then of course I'll turn Java stuff back on. Until then, you'll have to build Java support on your own.