| Summary: | openoffice-2.0.1 passes java-option wrongfully to configure | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Xake <kanelxake> |
| Component: | New packages | Assignee: | Gentoo Office Team <office> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | radek |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
No it doesn't. Just ignore the first message, this is from ooo-build, while we push the java-stuff directly to the the openoffice configure. So this is a non harmful "mistake" in reporting, but nothing relevant. If you want to see if java is disabled, you'll have to look a little bit later in the logs what the actual openoffice-configure run reports. This should work fine, it does here. btw: Which version are you actually trying to build? While the title of the bug says 2.0.1, you state 2.0.2 (which does not exist until now) in the report. Cause 2.0.1 actually should build fine with sun-jdk-1.5 (while 2.0.0 did not) Ok, found what you meant. And I meant 2.0.1, did wrote the wrong thing. So this bug is with other words invalid? My buildproblems should be another bug, right? Yes and yes ;) Closing this bug, as the problem is no problem at all. If you have a build problem with java-1.5 please file a new bug with more info about the actual build failure. |
I have a system with only gcc-4.0.2 and sun-jdk-1.5 merged. I tried to build openoffice-2.0.2 and when it failed I tried with USE="-java". One thing I noticed with this is that configure still reports: Building openoffice [snip] java: yes cd-ing into the building directory and entering ./configure gives me the same output, however adding --without-java changes the output to: Building openoffice [snip] java: no So shortly: The ebuild does for some reson not pass --without-java to configure as it should with USE="-java".