Bug 21090 – rmic conflict with J{DK,RE} and gcc with gcj

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description andy 2003-05-16 00:04:59 UTC]

rmic defaults to the default of gcc 3.2, even though java-config is set to
/opt/sun-jdk-1.4.1.02.

Reproducible: Always
Steps to Reproduce:
1. # emerge sun-jdk
2. > which rmic


Actual Results:  
didn't find rmic

Expected Results:  
should've found rmic :P

[Comment 1 Adrian Almenar 2003-07-01 20:44:12 UTC]

Im not having enough time to work on gentoo NOW, i can help on these later.

[Comment 2 Adrian Almenar 2003-11-20 07:36:52 UTC]

A little workaround for this now its using java-config --exec=rmic.

We know that this should be fixed, just helping while it gets fixed.

[Comment 3 Adrian Almenar 2003-12-10 03:31:38 UTC]

*** Bug 35490 has been marked as a duplicate of this bug. ***

[Comment 4 Christian Gut 2004-01-07 11:20:50 UTC]

to resolve this, i think the env.d file java-config generates should generally precede the one of gcc to resolve this problem

[Comment 5 Alan Schmitt 2004-04-18 22:17:05 UTC]

The fix should also include rmiregistry:

charm root # java-config -L
[blackdown-jdk-1.4.1] "Blackdown JDK 1.4.1" (/etc/env.d/java/20blackdown-jdk-1.4.1) *
charm root # which rmiregistry
/usr/i686-pc-linux-gnu/gcc-bin/3.3/rmiregistry
charm root # which rmic
/usr/i686-pc-linux-gnu/gcc-bin/3.3/rmic

[Comment 6 Karl Trygve Kalleberg (RETIRED) 2004-08-22 09:39:54 UTC]

This bug is intrinsic to gcc compiled with gcj. There's a patch against gcc for
this:
http://article.gmane.org/gmane.comp.gcc.patches/68352/match=fitzsim+jpackage

We should include it, to avoid doing really nasty workarounds.

[Comment 7 Saleem Abdulrasool (RETIRED) 2005-02-04 15:29:55 UTC]

This is a gcc related issue, but we can keep an eye on it.  The toolchain people are better oriented to solve this issue.

[Comment 8 SpanKY 2005-12-02 16:30:36 UTC]

gcc-4.0+ renames the utils