The 1.3.1 release has the 'cut' fix, the next release of 1.3.1 (rc2)
has the final floating stack code that was needed.
Alternatively set LD_ASSUME_KERNEL=2.2.5 when running Java and it will
use the backward compatability libraries with Redhat 7,1 , this will work
for 1.3.0_002 as well,
There are bugs logged on the JDC and the workaround above are listed there.
regards
calvin
"Alexander V. Konstantinou" wrote:
>
> I just upgraded a test machine running RedHat 6.2 (with all the latest
> updates) to RedHat 7.1. I'm having trouble getting Sun JDK 1.3.0_02 to work
> in the new environment (blackdown 1.3.0-FCS works as far as I've tested).
>
> Has anyone tried using Sun's JDK in RedHat 7.1 ? I'd like to find out
> if it is an upgrade issue, or a generic RH7.1 issue.
>
> Here are some details: Off the box I run into the following problem :
>
> /usr/local/java/sun-jdk1.3.0_02/bin/java: /usr/bin/cut: No such file or directory
>
> In RedHat 6.2 /usr/bin/cut is part of the textutils package. I found
> out that the utility has moved to /bin in RedHat 7.1 so I added a link
> from /bin/cut to /usr/bin/cut (ln -s /bin/cut /usr/bin/cut).
>
> Invoking "java -version" at this point would never return. strace reports:
>
> ...
> nanosleep({0, 1000000}, {3076, 0}) = 0
> nanosleep({0, 1000000}, {3076, 0}) = 0
> nanosleep({0, 1000000}, {3076, 0}) = 0
> nanosleep({0, 1000000}, {3076, 0}) = 0
> nanosleep({0, 1000000}, {3076, 0}) = 0
> ...
>
> manticore:bin> ldd i386/native_threads/java
> libpthread.so.0 => /lib/i686/libpthread.so.0 (0x40018000)
> libhpi.so => not found
> libjvm.so => not found
> libdl.so.2 => /lib/libdl.so.2 (0x40040000)
> libc.so.6 => /lib/i686/libc.so.6 (0x40044000)
> libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40174000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> manticore:bin> rpm -qa | grep glibc
> compat-glibc-6.2-2.1.3.2
> glibc-2.2.2-10
> glibc-common-2.2.2-10
> glibc-devel-2.2.2-10
> glibc-profile-2.2.2-10
>
> Thanks,
>
> Alexander V. Konstantinou
> [EMAIL PROTECTED]
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
