I try to use eclipse, so I emerged eclipse-sdk.
But it failed while building eclipse-ecj-3.4-r3.

The error message is like below.

 *
 * ERROR: dev-java/eclipse-ecj-3.4-r3 failed.
 * Call stack:
 * ebuild.sh, line   49:  Called src_compile
 * environment, line 3769:  Called die
 * The specific snippet of code:
 * [[ -x ${jar} ]] || die "No jar found for gcc";
 * The die message:
 * No jar found for gcc
 *
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/dev-java/eclipse-ecj-3.4-r3/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/dev-java/eclipse-ecj-3.4-r3/temp/environment'.
 *


And I found something on
"/var/tmp/portage/dev-java/eclipse-ecj-3.4-r3/temp/environment".
It try to find gjar or fastjar on ${gccbin}

local gccbin="$(gcc-config -B $(ls -1r /etc/env.d/gcc/${CHOST}-* | head -1)
|| die)";
local gcj="${gccbin}/gcj";
javac="${gcj} -C -encoding ISO-8859-1";
jar="${gccbin}/gjar";
[[ -x ${jar} ]] || jar="${gccbin}/fastjar";
[[ -x ${jar} ]] || die "No jar found for gcc";
java="${gccbin}/gij";


But my gcc has no gjar or fastjar.
My gcc's information is as below.

$ emerge -pv gcc

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] sys-devel/gcc-4.2.4  USE="fortran gcj gtk libffi mudflap nls
objc objc++ objc-gc openmp (-altivec) -bootstrap -build -doc (-hardened)
-ip28 -ip32r10k (-multilib) -multislot (-n32) (-n64) -nocxx -test -vanilla"
0 kB


And eclipse-ecj's

$ emerge -pv eclipse-ecj

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] dev-java/eclipse-ecj-3.4-r3  USE="gcj -java6" 0 kB



My friend use gentoo, and he use gcc 4.3.x. There is a gjar on gcc.

So, I think that eclipse-ecj try to use gcj, but my gcc version is older
than 4.3.x.
Am I right?
If this is right, it's a bug, I think. Because eclipse-ecj-3.4-r3 just only
check whether gcc has gcj flag or not, now. But it must be check gcc's
version, too(I'll try to report this on bugzilla).
If I'm wrong, is there any mistake?
Please let me know.

-- 
SOrCErEr

Reply via email to