Bug 34474 – openoffice-ximian blindly configures with --disable-java

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Jonathan Nall 2003-11-26 16:00:28 UTC]

when i emerge openoffice-ximian (specifically openoffice-ximian-1.1.46) i am not
able to use any of the features of openoffice that use java (e.g. JDBC). this
seems to happen due to the fact that the ebuild blindly configures the package
with --disable-java. this happens even though i have "java" in my USE variable.
further, it seems that since openoffice was compiled with --disable-java, it is
impossibly to even add runtime java support once the package is installed (i.e.
/opt/Ximian-OpenOffice/program/jvmsetup does not exist).



Reproducible: Always
Steps to Reproduce:
1. USE="java" emerge openoffice-ximian
2. run oowriter
3. try and access JDBC functionality

Actual Results:  
I get errors due to the fact that openoffice doesn't have a runtime JRE
associated with it.

Expected Results:  
If i have java in my USE flags, the package should be compiled with full java
support, and dependencies, etc should reflect what is needed for that support.

[Comment 1 Mitchell 2003-11-27 21:23:24 UTC]

I am also having a similar problem with openoffice-ximian-1.1.46 because Java is not a USE flag or required for the ebuild.  If a jdk is not installed, xlst needs to be installed and it is required in the ebuild.

[Comment 2 Andreas Proschofsky (RETIRED) 2004-01-14 02:46:18 UTC]

There is a new version (1.1.49.2) in portage now, please try that and report if your problem persists, it should have some java related bugs fixed

An explanation: --disable-java should only have an effect on the compilation process not on runtime features. Also we wont be enabling the java build process again, as it creates lots of problems.

[Comment 3 Paul de Vrieze (RETIRED) 2004-01-24 12:18:44 UTC]

If we are wrong and there is a part that is not involved in the build process we would be happy to reenable it. It is the use of java for transformations which does create many problems.

[Comment 4 Andreas Proschofsky (RETIRED) 2004-01-24 13:28:02 UTC]

I stand corrected on comment #2: Actually java functionality is only possible if we reenable java in the build system, otherwise jvmsetup is not even built, so you can't choose your jdk, sorry for the mistake.

Anyway there are two options:

*) Wait for Ximian to fix this problem (altough I don't know if this is in the works / possible)
*) Introduce a local use flag to enable java in the build system (only for the people that REALLY know what they are doing and not for everyone who has java on his/her system and don't need this functionality)

At the moment I tend to opt for option 1, because 2 will make maintaining the ebuild a lot more difficult (essentially I would have to test every version with the two different build systems). 

[Comment 5 Andreas Proschofsky (RETIRED) 2004-08-21 12:43:35 UTC]

won't fix this atm

[Comment 6 Andreas Proschofsky (RETIRED) 2004-09-06 07:35:50 UTC]

There is now a version in portage which builds the java functionality again (depending on if you have java installed): openoffice-ximian-1.3.3-r1 , it's hard-masked for now, please test if it works for you

[Comment 7 Andreas Proschofsky (RETIRED) 2004-09-26 23:15:34 UTC]

Closing this, should be fixed now