If gcc is compiled with the gcj flag, it will break all other Java SDKs if the user attempts to do development of RMI code. The reason is that gcc provides jar, rmic and rmiregistry, which is always added to the path before the java paths (and this is reasonable!). This problem has been recognized by the gcc people and they've written a patch for, that will become part of mainline for at least 3.5 Can we backport this to 3.3.3 and 3.4.x, to avoid unsensible workarounds? See: http://thread.gmane.org/gmane.comp.gcc.java.patches/7056
http://dev.gentoo.org/~cyfred/tmp/unofficial-for-review-gcc34-gjar-backport.patch Backported patch which I just finished building gcc 3.4.1 with... Backporting to the 3.3 series will be harder. I think the name of the patch says it all, but it will apply at the end of an ebuild unpack.
Revise that, the binaries still dont get the right names... *puzzled*
attach a patch to the bug, URL is 403
