Ivan Yosifov wrote:
> Ok...
>
> I updated migration overlay to revision 2153. Reemerged and updated both 
> java-config and java-config-wrapper. I now have java-config 2.0.22 and 
> 1.3.0-r2 installed, java-config-wrapper is 0.8-r2. /usr/bin/java-config is:
>
> #!/bin/bash
>
> WANT_JAVA_CONFIG=${WANT_JAVA_CONFIG:="2"}
>
> JAVA_CONFIG="/usr/bin/java-config-${WANT_JAVA_CONFIG}"
>
> if [[ -x ${JAVA_CONFIG} ]]; then
>         exec ${JAVA_CONFIG} "$@"
> else
>         echo "ERROR: Expected to find ${JAVA_CONFIG}"
>
> While emerging eclipse I (still) get:
>
> home ~ # emerge -1 eclipse-sdk
> Calculating dependencies... done!
>   
>>>> Emerging (1 of 1) dev-util/eclipse-sdk-3.1.2-r2 to /
>>>> checking ebuild checksums
>>>> checking auxfile checksums
>>>> checking miscfile checksums
>>>> checking distfiles checksums
>>>>         
>  * Checking for at least 768MBytes RAM ...                                                                            
> [ ok ]
> true
>  * Found offending option -fomit-frame-pointer in your CFLAGS
>
>  * One or more potentially gruesome CFLAGS detected. When you run into 
> trouble,
>  * please edit /etc/make.conf and remove all offending flags, then recompile
>  * Eclipse and all its dependencies before submitting a bug report.
>
>  * In particular, gtk+ is extremely sensitive to which which flags it was
>  * compiled with.
>
>  * Tip: use equery depgraph "=eclipse-sdk-3.1.2-r2" to list all dependencies.
>
> Cannot find JAVA_HOME in config file /etc/env.d/java/22sun-j2ee-1.3.1
> Cannot find JAVA_HOME in config file /etc/env.d/java/22sun-j2ee-1.3.1
> Detected a JDK < 1.5.0
> Cannot find JAVA_HOME in config file /etc/env.d/java/22sun-j2ee-1.3.1
> Detected a JDK >= 1.4.2
>   
>>>> Unpacking source...
>>>>         
>
> The env file seems to come from dev-java/sun-j2ee-1.3.1-r3 but that should be 
> an unrelated problem. Please correct me if I am wrong but line 91 of 
> java-utils.eclass:
>   
That thing about complaining about JAVA_HOME not found in some env files 
is a known issue in bugzilla somewhere.
> local vm_patch=$(echo ${vm_version} | cut -d. -f3)
>
> _really_ expects a 3-component vm_version, like 1.2.3. And here java-config -f 
> returns sun-jdk-1.5, that means a 2-component version "1.5". I described that 
> my last mail and still feel this is the issue at least in my case.
>
>   
You'll need to run java-config-1 -f. java-config reads WANT_JAVA_CONFIG 
variable to decide which one to actually run (java-config-1 or 
java-config-2), and by default it uses java-config-2.

Another thing to try is adding inherit java-pkg to the ebuild. The 
eclipse plugin doesn't currently inherit it, but the java-pkg.eclass 
from migration-overlay  has a few bits for coping with generation-2 
being around.

I also might suggest coming into #gentoo-java on freenode to help work 
this out, seeing as this thread has been dragging on and hasn't quite 
been resolved yet.

- Josh

-- 
gentoo-java@g.o mailing list