Re: Sorry, but
In message <[EMAIL PROTECTED]>, Steve Cohen writes: I read your README.linux and your strong suggestion to send bugs via the java-linux.org. Steve, Whups, we've not updated this! The java-linux.org site isn't active any longer. Please use http://www.blackdown.org/java-linux.html instead. To report bugs, visit http://www.blackdown.org/cgi-bin/jdk I downloaded jdk-sbb-1.1.6-2.1.2glibc.i386.rpm for my RedHat 5.0 system. This system has never had the jdk on it before. I used rpm to install it to the default location. But the symbolic links are all wrong. Have you updated your 5.0 system with the ld and glibc RPMs mentioned on http://www.redhat.com/support/docs/rhl/rh50-errata-general.html? If not, something odd must be happening, but I think I'll defer this question to the RPM maintainer. The two people I know of who are making RPMs have both been *very* responsive to problem reports. In the meantime, you may wish to download the plain tar file from one of the mirrors mentioned at http://www.blackdown.org/java-linux/mirrors.cgi. Once you've gotten it over to your system, simply type "tar zxvf FILENAME" in the directory you wish to install the JDK. Then set your JAVA_HOME and CLASSPATH environment variables (unsetting JDK_HOME or anything else like that as well). Some instructions for how to do all this are found at http://www.blackdown.org/java-linux/docs/faq/FAQ-java-linux-3.html. Good luck!
Re: 1.1.6-libc under redhat 5?
In message <[EMAIL PROTECTED]>, "J.P.Lewis" writes: Hello, can I run the libc version of 1.1.6 under plain redhat 5 We haven't tried in a long time, and we don't recommend it. I think RedHat's support team wouldn't recommend it, either :)
Re: A shift-key problem
In message <[EMAIL PROTECTED]>, Darius Bacon writes: In awt's KeyEvents the shift key is not being recognized -- event.isShiftDown() is false when it should be true. This is with Swing 1.0.2 and JDK 1.1.6 v2 for libc5, under RedHat release 4.1 with kernel 2.0.27. Darius, A solution is on the way. Professor Kevin Hendricks of the college of William and Mary in association with the Glyph have come up with a fix for this problem. The patch also fixes the lack of numeric keypad support. (Please see http://business.tyler.wm.edu/mklinux/files.html for more details.) But read on... Unfortunately, none of our schedules have permitted us to generate a fresh i386 build for release at this time. Please stay tuned! At any rate, this is a great time to say "thank you" to Kevin for these and many other fixes (which the PPC people can already use).
Sorry, but
I read your README.linux and your strong suggestion to send bugs via the java-linux.org. But when I tried to do as you suggested, subscribe to the list, I get told Host unknown (Name server: java-linux.org: host not found) Has it moved? Since that doesn't work, I will reluctantly ask you the question. Probably you don't know the answer but maybe you can direct me or forward this message to the person who does: I downloaded jdk-sbb-1.1.6-2.1.2glibc.i386.rpm for my RedHat 5.0 system. This system has never had the jdk on it before. I used rpm to install it to the default location. But the symbolic links are all wrong. Every executable (for example, javac) I try to run brings up a message like this: javac was not found in /usr/bin/jdk-1.1.6/../bin/i586/green_threads/javac Fiddling with my path does no good either. How should I best proceed? Steve Cohen
Problem with jdk1.1.3
A shift-key problem
In awt's KeyEvents the shift key is not being recognized -- event.isShiftDown() is false when it should be true. This is with Swing 1.0.2 and JDK 1.1.6 v2 for libc5, under RedHat release 4.1 with kernel 2.0.27. Has anyone else seen this, or have any clues? Thanks, Darius
Print Error
Whenever I try to print directly from a Java program on Linux I get: "Print Error" "Could not execute print commands: [Ljava.lang.String;@80cc814]" It works fine if I direct the print output to a file and then print the file from the command line. I even copied a simple example from a text book. I worked fine on Win95 but gave the same error on Linux. Do I need to specify special 'Print Command Options'? My default printer is 'lp'. Gary Mart [EMAIL PROTECTED]
1.1.6-libc under redhat 5?
Hello, can I run the libc version of 1.1.6 under plain redhat 5 (rather than downloading the glibc and its antecedants, which would be a big project with my unreliable net connection) --- j.p.lewis [EMAIL PROTECTED] 012 345 6789 //www.idiom.com/~zilla
1.1.6-libc under redhat 5? (fwd)
Alternate question: with 1.1.6-v2 do I need to upgrade a plain Redhat5 to the new glibc/ld/etc? The FAQ talks about this, but I don't understand what it is saying: "The latest versions of the Blackdown JDK have their own built-in loader and libc, which will hopefully make them more robust. Older versions of the JDK 1.1.5 (especially) are much more sensitive. Karl Asha maintains a list JDK-related library issues at: http://www.blackdown.org/java-linux/docs/libraries.html. In short, you need glibc-2.0.7 and glibc-devel-2.0.7 or higher on a glibc-based system such as RedHat 5.0 or Debian 2.0." -- Forwarded message -- Hello, can I run the libc version of 1.1.6 under plain redhat 5 (rather than downloading the glibc and its antecedants, which would be a big project with my unreliable net connection) --- j.p.lewis [EMAIL PROTECTED] 012 345 6789 //www.idiom.com/~zilla
1.1.6-v2 problem with swing textinput
On an i386 redhat5.0 system, I'm developing a swing1.02 program. It works ok under jdk1.1.5v5-980311. Under 1.1.6-v2-glibc, various problems with text input in a jtable cell: - double characters - does not end editing, rather it enters as an unprintable character - likewise del and backspace do not function - after editing the cell once, double characters do nnot appear during subsequent edits; likewise del and backspace work (glibc2.0.7-13 ld.so1.9.5-5) Thanks for any thoughts --- j.p.lewis [EMAIL PROTECTED] 012 345 6789 //www.idiom.com/~zilla
problem/fix
I downloaded the jdk1.1.6-v2-i386 and unpacked it. On a Pentium, everything worked fine, but on a Pentium 2, the javac (along with with javap, javadoc, javakey, etc...) would immediately complain: **Out of memory, exiting** after some mucking around, I ended up removing all the "-ms8m" from all the scripts in $JAVA_HOME/bin/i586/green_threads/ and it doesn't complain... is thre a better fix? jon
