When emerging dev-java/sun-jdk-1.6.0.06 it fails here: * Creating the Class Data Sharing archives /var/tmp/portage/dev-java/sun-jdk-1.6.0.06/work/jdk1.6.0_06/bin/java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory As this error didn't appear on any other computer and I found no bugs about it I did some experimenting to try to find why. Unfortunately I can't tell why it works on all other systems and it fails on that one but here some information. - There is dev-java/sun-jdk-1.4.2.17 already installed, installing dev-java/sun-jdk-1.5.0.15 works and does not change the result on 1.6.0.06. - On another computer it emerges correctly when sun-jdk-1.4.2.17 is already installed or when there is no other jdk at all. - It can be emerged with this workaround: LD_LIBRARY_PATH=/var/tmp/portage/dev-java/sun-jdk-1.6.0.06/work/jdk1.6.0_06/jre/lib/i386/jli/ emerge sun-jdk - when once installed it can still not be reemerged using only emerge sun-jdk - running installed java on the command line still does not find this library (after java-config -S 2), interestingly java-check-environment reports all OK. - I compared /etc/ld.so.conf of working and not working computer and found no significant differences (and no references to v1.6). - on not-working machine: ldd /opt/sun-jdk-1.6.0.06/bin/java linux-gate.so.1 => (0xffffe000) libpthread.so.0 => /lib/libpthread.so.0 (0xb7f5b000) libjli.so => not found libdl.so.2 => /lib/libdl.so.2 (0xb7f57000) libc.so.6 => /lib/libc.so.6 (0xb7e32000) /lib/ld-linux.so.2 (0xb7f8f000) On working machine it's the same except: libjli.so => /opt/sun-jdk-1.6.0.06/bin/../jre/lib/i386/jli/libjli.so I have no clue why on the one machine it uses the relative path and on the other this seems not to work. The problem existed before an update and after emerge -uND world it is still there. So I'm currently out of ideas where to look for the source of the problem and why it works on some computer and on this one not. The ebuilds are the same, dated May 22. The only location of the "missing" library on the working systems is /opt/sun-jdk-1.6.0.03/jre/lib/i386/jli/libjli.so which is of course not present before the installation of sun-jdk. Any ideas?
Created attachment 155881 [details] emerge --info
Try mounting /proc :) *** This bug has been marked as a duplicate of bug 165330 ***
(In reply to comment #2) Sorry for the duplicate, but when I searched the bugs with "ALL sun-jdk libjli.so" , "ALL libjli.so" and similar there were none suitable found :-(. Now there are the two :-). By the way, mounting proc resolves the problem here. I wasn't aware that ld needs proc to resolve relative path names. IMHO making the ebuild to check for mounted proc would be a good idea as emerging will definitely fail in case it's not mounted. Or set LD_LIBRARY_PATH if this makes more sense than failing with a descriptive message.
