Hi Folks
My problem: my system does not run jdk1.2.2 v3.
Has anyone built a .deb from the Blackdown tarball? The .debs
install and run. I have searched Blackdown and debian.org for java
1.2 .debs for any version of Debian, but there is no joy in
Muddville tonight.
There were several responses to my earlier query which I very much
appreciate, but there is still no joy. Everyone who answered my
earlier inquiry agree with the README that installation is trivial.
This has not been my experience. My experience with the tarball
r3 from Blackdown follow:
I have a stock Slink system running on a K6 350 100 MHZ MB 128 MB
RAM, 8G ide drive, SiS 6326 8MB video. I have jdk1.1 deb package
installed. I need jdk1.2
I downloaded jdk1.2.2 r3 from blackdown, untarred it in /usr/local.
I set the path per install instructions from blackdown:
export PATH=/usr/bin/jdk1.2.2/bin:$PATH
Attemtping to run java from here fails:
java
or
cd /usr/local/jdk1.2.2/bin
#./java
each result in the following errors:
./java: /bin/realpath: No such file or directory
./java: /bin/realpath: No such file or directory
java was not found in /bin/i386/native_threads/java
The libhpi.so in Release Candidate #3 appears to require symbols
that are not libc on my Slink system. The result is that the
scripts that need a version of realpath in the jdk fail, so nothing
is found. I concluded this after hacking the script.
I hacked this script a bit to find where it failed. It fails at the
realpath in the jdk, returning the null string when called a path.
I replaced the path to the version of realpath that came with
jdk1.2.2 with the path to the realpath already on my system. This
time the path to the libraries is correct. I echo'd the value of the
variable. The script sets LD_LIBRARY_PATH so the linking loader can
find the shared java libraries, but the symbol I mention is not
resolved, and my attempt to run java fails.
The symbols that remains unresolved on my home system are
__libc_current_sigrtmax and __libc_current_sigrtmin
These occur in libhpi.so, in the library
/usr/local/jdk1.2.2/jre/lib/i386/native_threads/libhpi.so
Do I need to upgrade my libc? The README suggests that this release
fails 'early versions of libc2' and remarks that the build was made
on a Potato system.
etting an earlier version
of the jdk means taking a stack of floppies tot he office and using
split ...
If you know how far back I have to go to get a usable version of
the jdk (v1? v2?) I would appreciate some advice.
If this is not the appropriate forum for this question, please point
me some place else.
--David
David Teague, [EMAIL PROTECTED]
Debian GNU/Linux Because software support is free, timely,
useful, technically accurate, and friendly.
(I'm hoping the answer will be all of the above!)
