Emerging openoffice with Sun's jdk as default will cause the following error: ---------- * * This ebuild has only been tested with the blackdown port of * java. If you use another java implementation, it could fail * horribly, so please merge the blackdown-jdk and set it as * system VM before proceeding: * * # emerge blackdown-jdk * # java-config --set-system-vm=blackdown-jdk-<VERSION> * # env-update * # source /etc/profile * * Please adjust <VERSION> according to the version installed in * /opt. * * If you however want to test another JDK (not officially supported), * you could do the following: * * # export FORCE_JAVA=yes * !!! ERROR: app-office/openoffice-1.1.3 failed. !!! Function pkg_setup, Line 109, Exitcode 0 !!! (no error message) ---------- This is easily worked around by running java-config --set-system-vm=blackdown-jdk-<VERSION> as suggested, but it is disturbing and breaks background system updates. Is it really not possible to make the ebuild change the dafault java compiler just for the OO compile, or something like that? Reproducible: Always Steps to Reproduce:
Actually the openoffice compile should work with all jdk's. Maybe we'll drop the check. At least the sun one works fine as I normally use that one. (the 1.5 version might be problematic though)
Yes, I recently emerge openoffice-1.1.3 with FORCE_JAVA=yes, having only the official SUN JDK 1.4.2_06 installed. Works flawlessly here.
I removed the java check in 1.1.3-r1 (it also builds fine for me with sun-jdk) Closing this
