On Wednesday 10 September 2003 02:31 pm, HvR wrote: > i did emerge sync > then emerge -u system > it decided to download sys-libs/db-4.0.14-r2 > but the compilation fails at > !!! Function src_compile, Line 64, Exitcode 1 > !!! (no error message) > > now what do i do? > > (it has happened on both my gentoo systems) Oh, boy, good timing is everything!
I just found this problem myself about 15 minutes ago, and I think I've solved it: I noticed that some error messages further up on the screen said something about "no acceptable javac." I did a "which javac" on the command line, and sure enough, javac wasn't in the path. I checked in the Sun JDK installation and javac seemed to be there, in: /opt/sun-jdk-1.4.2.1/bin I made a symbolic link in /usr/bin to the javacc here: ln -sf /usr/bin/javacc /opt/sun-jkd-1.4.2.1/bin and reran the emerge command. However, it still didn't work - I got the same error message, but this time it was complaining abou It not finding a suitable "jar." I did a "which jar" and sure enough, it wasn't in the path.: which: no jarr in (/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/opt/bin: /usr/i686-pc-linux-gnu/gcc-bin/3.2:/opt/Acrobat5:/usr/X11R6/bin: /opt/sun-jdk-1.4.2/bin:/opt/sun-jdk-1.4.2/jre/bin:/opt/sun-jdk-1.4.2/jre/javaws: /usr/qt/3/bin:/usr/kde/3.1/sbin:/usr/kde/3.1/bin) But then I noticed that the java directories in the path were under "/opt/sun-jdk-1.4.2" and not "/opt/sun-jdk-1.4.2.1". It turned out that the "/opt/sun-jdk-1.4.2/" direcotry tree was nearly empty. I deleted that and renamed /opt/sun-jdk-1.4.2.1 to /opt/sun-jdk-1.4.2, and reran the emerge command. It worked great. I don't know why my sun-jdk directories got those funny names. Maybe it was a remnant of a failed "emerge sun-jdk". Anyway, check and see if you might have the same thing going on. Tony -- [EMAIL PROTECTED] mailing list
