Briefly if you've upgraded to blackdown-jdk-1.4.1 from the 1.4.1_beta the kdebase build fails. There is a fix. The remains of the blackdown-jdk_1.4.1_beta directories (they were empty in my case) need to be removed. Then I created a symlink in the opt directory, 'blackdown-jdk-1.4.1_beta' pointing to the the 'blackdown-jdk-1.4.1' directory inside the opt directory. This is not an optimal fix of course but I was anxious to see how much better kde 3.1.1 is .. It might be that a simple config file problem exists on my machine giving the wrong default java info .. i have not looked yet .. but this will catch others as well so a fix is needed somewhere. derk
back again seems the problem may be with the blackdown-jdk-1.4.1 ebuild and the removal of the 1.4.1_beta config files. BD-jdk-1.4.1 adds a directory to /etc/env.d with all it's info but the '20java' file from the BD-1.4.1_beta is still there in all it's glory telling etc-update that it still exists. I've edited that file to remove all the '_beta' but perhaps this file can be pitched entirely? derk
The java env.d files should be edited with java-config. Don't touch them manually. Run java-config --help to see how to use it. Then set your system vm to blackdown-jdk-1.4.1 or whatever you have now. Does kde work then?
once the java problem was fixed kde 3.1.1 compiled .. i'm now at kde 3.1.1-r1 w/ the latest qt ('~x86' versions) w/o problems. I've since run java-config and all seems well. Any idea why the upgrade did not run java-config auto-magicly? derk
java-config doesn't get automatically get updated. I'm assigning this to the java people so they can see whether they want to update their ebuilds do something when unmerging the current java.
*** Bug 25703 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 22395 ***
