Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 161484 - Reason for openoffice-2.0.4 depending on jre/jdk-1.5 and not 1.6?
Summary: Reason for openoffice-2.0.4 depending on jre/jdk-1.5 and not 1.6?
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-11 08:52 UTC by Patrick
Modified: 2007-03-05 20:34 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick 2007-01-11 08:52:33 UTC
Well, title says it all. As sun-jdk/jre-1.6.* are in ~x86, and openoffice-2.0.4 is, too, I don't see a reason for having openoffice-2.0.4 depending on the 1.5 java. Both should be possible - depend on 1.5 or 1.6, at least one of them must be installed.

Reproducible: Always

Steps to Reproduce:
1. Have sun-jdk-1.6* and sun-jre-1.6* installed
2. Try to merge openoffice

Actual Results:  
emerge wants to pull in slotted sun-jdk-1.5* and sun-jre-1.5*

Expected Results:  
emerge is happy with java 1.6, because openoffice-2.0.4 works perfectly with it, afaik.
Comment 1 Patrick 2007-01-11 09:10:43 UTC
Sorry, now that I actually tried it myself, I found this during configure:

checking whether to build with Java support... yes
checking the installed JDK... checked (JDK 1.6.0)
checking for target java bytecode version... 1.6
configure: error: 1.6 is not supported java bytecode version!

Strange, because I ran openoffice-bin-2.0.x with Java 1.6* iirc, without any problem.
Comment 2 Petteri Räty (RETIRED) gentoo-dev 2007-03-05 20:32:56 UTC
(In reply to comment #1)
>
> Strange, because I ran openoffice-bin-2.0.x with Java 1.6* iirc, without any
> problem.
> 

Although Sun strives to be binary compatible with earlier releases, does not mean that their API would be. In your case it's very much safe to run binaries compiled with 1.5 on 1.6 though I am guessing OO works just fine with 1.6 and they mean to catch <1.5 with this test.