JDK-4414722 : v1.3 won't work on Redhat 7.1 BETA (Fisher): GLIBC version 2.2.1-3.i686 problem?
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.3.0
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: x86
  • Submitted: 2001-02-13
  • Updated: 2001-02-18
  • Resolved: 2001-02-18
Related Reports
Duplicate :  
Description

Name: krC82822			Date: 02/13/2001


13 Feb 2001, eval1127@eng -- see also:
http://search.java.sun.com/query.html?qt=%2Blinux+%2B%22hard-coded%22&col=obug&qp=&qs=&qc=&pw=100%25&ws=0&qm=0&st=1&nh=10&lk=1&rf=0&rq=0


None of the Java 2 SDK tools can execute on Redhat 7.0.99 (otherwise known as
Redhat 7.1 BETA or Fisher).

The following error message appears when executed on a "clean" install of Redhat
Fisher and the J2SDK:

/usr/java/jdk1.3/bin/java: /usr/bin/cut: No such file or directory
/usr/java/jdk1.3/bin/i386/native_threads/java: error while loading shared
libraries: libjvm.so: cannot load shared object file: no such file or directory

When "cut" is then added to the "/usr/bin" directory, any execution of the same
java tools then results in that tool being frozen (actually, "top" reports the
process as "sleeping").

This seems to be a problem with the GLIBC version 2.2.1 libraries for the i686
build (PIII, Athlons).
(Review ID: 116875) 
======================================================================

Comments
EVALUATION 18 Feb 2001, kevin.ryan@eng -- since #4415774 refers to RH 7.1 (not just 7.1 beta), am duping this bug to # 4415774.
11-06-2004

WORK AROUND Name: krC82822 Date: 02/13/2001 Forcing the use of glibc-2.2.1-3.i386.rpm (instead of glibc-2.2.1-3.i686.rpm) seems to solve the problem, athough threads are no longer executed "asynchronously" (All threads execute sychronized with the launching process). ======================================================================
11-06-2004