|Summary:||dev-java/sun-jdk-126.96.36.199-r2: Error: could not find libjava.so|
|Product:||Gentoo Linux||Reporter:||Toralf Förster <toralf>|
|Component:||Current packages||Assignee:||Java team <java>|
|Severity:||normal||CC:||andre, dominik.buerkle, jsled, lionel_sanchez, michael, miro_bogner, philipp.reinkemeier, sven.koehler|
|Package list:||Runtime testing required:||---|
|Bug Depends on:|
Description Toralf Förster 2006-01-19 10:59:42 UTC
After upgrading from dev-java/sun-jdk-188.8.131.52 rp -r2 I got: tfoerste@n22 ~ $ java -version Error: could not find libjava.so Error: could not find Java 2 Runtime Environment. :-( Problem seems to be related to the changed path i686 vs i386 : n22 /opt/sun-jdk-184.108.40.206/jre/lib # pwd /opt/sun-jdk-220.127.116.11/jre/lib n22 /opt/sun-jdk-18.104.22.168/jre/lib # java -version Error: could not find libjava.so Error: could not find Java 2 Runtime Environment. n22 /opt/sun-jdk-22.214.171.124/jre/lib # ln -s i686 i386 n22 /opt/sun-jdk-126.96.36.199/jre/lib # java -version java version "1.4.2_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03) Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
Comment 1 Bill Krueger 2006-01-19 11:36:24 UTC
I had the same problem as well (I use 1.4.2 and 1.5.0 installed if that matters) and doing an emerge =sun-jdk-188.8.131.52-r2 fixed it for me.
Comment 2 Josh Nichols (RETIRED) 2006-01-19 11:38:31 UTC
The ebuild should be installing that symlink for you. I seem to recall seeing this, but then it went away after re-emerging. I'm not sure why this happens exactly, but I would suspect it has to do with the i386 being a real directory in -r1, but a symlink in -r2. I could try keeping the original i386 directory, then symlinking that to i686.
Comment 3 Toralf Förster 2006-01-19 12:13:53 UTC
>I could try keeping the original i386 directory, then symlinking that to i686 During emerg of -r2 the directory i686 was created and portage removed the i386 directory during unmerge of the 184.108.40.206 package, so I symlinked i686 to i386 not vice versa
Comment 4 Sven 2006-01-19 12:43:19 UTC
Same error for me! There are also other problems: jsvc (the thing that's included in tomcat 5.5 to start tomcat as a daemon) doesn't find java anymore. An strance shows me, that jsvc also only looks in the i386 directory. The ebuild should really do "ln -s i386 i686" instead of "mv i386 i686".
Comment 5 Josh Sled 2006-01-19 13:46:54 UTC
Just wanted to echo another datapoint: emerge udatep from sun-jdk-1.5.0.06-r1 to -r2 broke in the same way; the `ln -s i686 i386` symlink initially seems to help...
Comment 6 ((RayDar)) 2006-01-19 14:55:59 UTC
For me, both the i386 and i686 directories existed. The only thing in the i386 directory was libjpisock.so. Renaming the i386 directory to i386.error before making the symlink named i386 that points to i686 seems to have fixed the problem for me.
Comment 7 Josh Nichols (RETIRED) 2006-01-19 16:13:04 UTC
Fixed in CVS. Please sync, unmerge =dev-java/sun-jdk-220.127.116.11-r2 , then re-merge =dev-java/sun-jdk-18.104.22.168-r2. You may get away without unmerging, but it would be on the safe side, so that emerge doesn't get confused about the symlinks. For the record, /opt/sun-jdk-22.214.171.124/jre/lib/i386 is no the actual directory, and that gets symlinked to i686. Sorry for the breakage folks.
Comment 8 Jakub Moc (RETIRED) 2006-01-20 07:14:20 UTC
*** Bug 119688 has been marked as a duplicate of this bug. ***
Comment 9 Andreas Proschofsky (RETIRED) 2006-01-23 07:49:26 UTC
*** Bug 120055 has been marked as a duplicate of this bug. ***
Comment 10 Andreas Proschofsky (RETIRED) 2006-01-23 22:37:51 UTC
*** Bug 120105 has been marked as a duplicate of this bug. ***
Comment 11 Jakub Moc (RETIRED) 2006-01-24 10:56:03 UTC
*** Bug 120206 has been marked as a duplicate of this bug. ***
Comment 12 Jakub Moc (RETIRED) 2006-01-26 01:48:29 UTC
*** Bug 120386 has been marked as a duplicate of this bug. ***
Comment 13 Jakub Moc (RETIRED) 2006-01-27 15:22:24 UTC
*** Bug 120556 has been marked as a duplicate of this bug. ***