This error comes always after emerge --sync. The ebuild file is wrong. I've used this Eclipse version for a quite long time now and it really doesn't need gcc 4.0 - gcc 3.4.3-20050110 works just fine. It's easy to fix, just remove the gcj-line from the ebuild dependencies. Reproducible: Always Steps to Reproduce: 1. Eclipse-sdk-3.1_pre6 installed & in world 2. emerge --sync 3. emerge -DuNtp world Actual Results: Calculating world dependencies | !!! All ebuilds that could satisfy ">=sys-devel/gcc-4.0.0_beta20050305" have bee n masked. !!! One of the following masked packages is required to complete your request: - sys-devel/gcc-4.0.0 (masked by: package.mask, -* keyword) # Jeremy Huddleston <eradicator@gentoo.org> (28 Jan 2004) # Added alpha 4.0 gcc by request for testing. It is not ready for prime time, # so if you use it and it breaks your system it's your fault. - sys-devel/gcc-4.0.1_beta20050507 (masked by: package.mask, -* keyword) For more information, see MASKED PACKAGES section in the emerge man page or section 2.2 "Software Availability" in the Gentoo Handbook. !!! (dependency required by "dev-util/eclipse-sdk-3.1_pre6" [ebuild]) !!! Problem with ebuild dev-util/eclipse-sdk-3.1_pre6 !!! Possibly a DEPEND/*DEPEND problem. Expected Results: no dependency errors My system: gcc 3.4.3-20050110 Sun jdk 1.5.0_03-b07 (doesn't compile with it, but can be used as a user java environment) 2005.0 profile
Just a gues (since you did not include `emerge info `) that you have gcj enabled. Try `USE="-gcj" emerge eclipse-sdk` and it should work without removing the gcj line. :)
Yes, I had the gcj enabled. I just wondered, why there is such a restriction, as the script really works with older gcj & gcc as well.
Well, i'm just guessing (again) but the 'gcj' USEflag here realy means that eclipse would be build with gcj (read: native binary) and not with javac. gcc is only used for the SWT part of eclipse.
Yeah, the gcj useflag was added while we were experimenting with building all of eclipse-sdk using it. We didn't finish this in time for 3.1 final release, so we've removed it now. Sorry for the inconvenience.
