When trying to emerge jedit, I get this error: emerge jedit Calculating dependencies ...done! >>> emerge app-editors/jedit-4.0 to / >>> md5 ;-) jedit40source.tar.gz >>> Unpacking source... >>> Unpacking jedit40source.tar.gz >>> Source unpacked. Buildfile: build.xml !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 1, Exitcode 1 !!! (no error message) !!! emerge aborting on /usr/portage/app-editors/jedit/jedit-4.0.ebuild . error in ebuild -- needs fix.
What virtual machine are you running? The ebuild works fine here.
won't emerge with sun-jdk-1.4.0. (switched back to sun-jdk-1.3.03 and it's fine.)
There is a new sun-jdk ebuild 1.4.0-r3... I'm running this ebuild and appears to work ok.
sun-jdk-1.4.0-r3 is what i used. hmmm. environment is setup correctly. i can compile the source manually using sun-jdk 1.4.0 using ant. are you sure it built for you? like i said before, I can emerge jedit using sun-jdk-1.3.03, but once you compile it with that, it can't be used with 1.4.0 unless you compile jedit a certain way (it's in the readme.) so, what the hell's wrong with mine, then? (for now, i'm just using the jar from jedit.org.)
It is a very good question... When did you merge 1.4.0-r3? there was a small bug in it for quite some time (about 14 hours), which was totally my fault, but is now fixed. You may want to merge again if you can. It was fixed at 6/16 18:59 CVS time.
ok, i did 'emerge rsync', then i just unmerged sun-jdk1.4.0, reemerged it. then i set the system vm to 1.4.0 just to be sure. env-update, and then i logged out and relogged in with the same user account. tried emerging jedit again -- no dice! same error again. am i doing something wrong? should I reboot and try? is anybody else having this problem?
No it appears you are doing eveything right... just for kicks what versions of jikes is merged?
jikes v 1.15
update: i just reinstalled gentoo from 1.1a (save for my /home partition and some config backups) and I can now emerge jedit with sun-jdk-1.4.0. my best guess what was wrong was that I either messed something up emerging/updating, etc, or that some tmp files where lying around messing things up (from ant or jikes.) not really sure, though. bottomline, this was not a problem with the ebuild.
