Red Hat Bugzilla – Bug 90755
Latest glibc packages break java
Last modified: 2016-11-24 10:18:37 EST
Description of problem: Latest glibc packages break java. Is there a -compat package somewhere ? Version-Release number of selected component (if applicable): [nim@ulysse nim]$ rpm -qa | grep glibc glibc-kernheaders-2.4-8.13 glibc-profile-2.3.2-37 glibc-common-2.3.2-37 glibc-devel-2.3.2-37 glibc-utils-2.3.2-37 glibc-2.3.2-37 How reproducible: Always Steps to Reproduce: 1. Update rawhide 2. Try to use java utils [nim@ulysse nim]$ /usr/lib/jvm/java-1.3.1-sun-1.3.1.08/bin/java -version Error occurred during initialization of VM Unable to load native library: /usr/lib/jvm/java-1.3.1-sun-1.3.1.08/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
/usr/lib/jvm/java-1.3.1-blackdown-1.3.1.02b/bin/i386/native_threads/java: relocation error: /usr/lib/jvm/java-1.3.1-blackdown-1.3.1.02b/jre/lib/i386/libjava.so: symbol __libc_waitpid, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
It is a bug in that ancient JDK, fixed in more recent JDK releases.
Unfortunately 1.3.1 is the target production java sdk for lots of people. With 1.4.0 quietly retired by Sun and 1.4.1 looking like it will have the same fate as soon as 1.4.2 is available people don't have much choice. And 1.3.1 *is* still updated regularly - the sun 1.3.1 sdk involved in the bug report was updated just a few days ago. However, that's your call
IBM java broken too [nim@rousalka nim]$ unset LANG [nim@rousalka nim]$ export LD_ASSUME_KERNEL=2.2.5 [nim@rousalka nim]$ /usr/lib/jvm/java-1.4.0-ibm/bin/java -version Unable to initialize signal handler, thread create failed Could not create the Java virtual machine.
All JVMs needed some help when using NPTL. Sun's 1.4.1 (I think) worked, IBM also eventually got a 1.4.1 version to work, maybe even backported the changes to a 1.3 version. This is in no case a glibc problem. Closing.