When mozilla is merged with -java in USE then mozilla is built without oji support and thus, the include files at /usr/include/mozilla/oji/ aren't installed. On the other hand, galeon fails to build if those include files aren't available, so oji should probably be used even with -java in USE (building oji does *not* require a JDK or JVM, it works even if no java environment is installed). To compile galeon properly the workaround for now is USE="java" emerge mozilla --nodeps (--nodeps so that you don't get the java stuff, it's not needed to build with oji, USE java so the eclass gives us oji headers) It seems that a recent change to mozilla.eclass (rev 1.8<-->1.9 ?) changed the oji behaviour, that's why using -java with mozilla and then compiling galeon worked before. This problem is not related to a specific version of mozilla or galeon, it can be reproduced (and worked around) with the most recent and older versions.
thanks, fixed in mozilla.eclass (and bumped to mozilla-1.7.2-r1 to carry out the change)
Can someone address the java use flag usage in the firefox ebuild. mozilla-firefox-1.5.0.3.ebuild has java as a use flag, but it's not used anywhere. Seems it might have been related to this bug, and the conditional of use java has been removed. So the java use flag is totally useless and does not seem to effect anything. Furthermore I recommend adding java-pkg to the inherited virtuals, along with calling java-pkg_pkg_setup in pkg_setup. To make sure proper jdk is used.
