Red Hat Bugzilla – Bug 27003
Sun's Java 2 1.3 broken
Last modified: 2007-04-18 12:31:24 EDT
java -version gives:
/opt $ java -version
/opt/jdk/bin/java: /usr/bin/cut: No such file or directory
/opt/jdk1.3/bin/i386/native_threads/java: error while loading shared
libraries: libjvm.so: cannot load shared object file: No such file or
Same error when calling javac
This version of Java worked fine on 7.0 Guiness
Assigning to glibc, but it looks very likely that your ld.so.conf
is screwed up.
I have had the same problem. I linked /bin/cut as /usr/bin/cut and the error
message disappeared, but java does not work yet.
We (Red Hat) should really try to resolve this before next release.
I have determined that this has something to do with glibc-2.2.1-3.i686:
When I forced the installation of glibc-2.2.1-3.i386.rpm, java started to
"work". Threads do NOT behave like threads, though (basically, there's no
java -version reports:
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
Java HotSpot(TM) Client VM (build 1.3.0, mixed mode)
The use of glibc-2.2.1-3.i686.rpm does work for Java SDK, version 1.3.0, when
using the (now obsolete) Classic VM (green-threads, no jit).
NOTE: This is the motherboard/processor I am running:
ASUS A7V (no audio) motherboard
Athlon Thunderbird Socket-A processor, 850MHz
128MB SDRAM (PC-133)
IBM Deskstar G30X 30GB HDD (ATA-100)
I hope this helps...
The reason is (probably) the use of an assumption that the thread stack space is
2 MB. This is a duplicate of something... searching.
*** Bug 27436 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 27090 ***