I am apparently who started this thread. I took everyone's suggestion and just now downloaded the updated glibc from RedHat named glibc-2.0.7-19.i386.rpm Suddenly jdk116_v5 started to work! If you're still having trouble, you can get it at ftp://sunsite.unc.edu/pub/Linux/distributions/redhat/updates/5.0/i386/ At 11:05 AM 10/15/98 -0400, Michael Sinz wrote: >On Thu, 15 Oct 1998 07:44:31 -0400, Jim Ridenour wrote: > >> First let me say I'm new to Linux, but I do run other programs on it >>successfully. >>I have two questions: >> >>1. On Blackdown's mirror sites for JDK116_v5 they have two files beginning >>with jdk... and differing only by the letter "b" toward the end. The one >>without the "b" appears to be the one I want and uncompresses to the JDK. >>The one with the "b" on the end won't even uncompress. What is it? > >We have started to release the files in both tar.gz and tar.bz2 format. >The bz2 compression format (bzip2) is a new compression system that >happens to do a nice job on the JDK (saving a bit over 10% in size and >since the archive is over 10megs that means over 1meg smaller archives) > >Many people do not have bzip2 support on their systems. Plus, tar.gz >is a well established format that works on almost all platforms (including >Windows/WinZIP) tar.gz also uses much less RAM to decompress a file. >(bzip2 can use a lot of memory to do a decompress and the memory it >takes depends on the way the file was compressed) > >The main reason we are trying bzip2 format is to see if people really >want it due to the smaller file sizes. (Not all files are smaller) >I know it takes me twice as long to upload the two different formats >and thus I would like to have only one, but since I do the upload in >auto-pilot mode while I am away from my machines usually, it does not >bother me too much) > >>2. Having uncompressed JDK116v5 (the one without the "b" at the end) it >>creates all the directories to hold the jdk. If I go into /jdk116v5/bin >>and create a test.java file and then invoke "javac test.java", nothing >>happens. I just get a command prompt back. No test.class file is created, >>no errors, no messages, nothing. Both the test.java and the javac are in >>that directory so paths shouldn't be the problem. Any ideas? > >Hmmm... I don't have an idea right now. I normall add the jdk116v5/bin >directory to my path and do my work elsewhere. > >>PS I should say this is on RedHat 5.0 and I used their package manager to >>remove all Kaffe files. Also, I am using the glibc version which by the >>tests Blackdown describes for telling which library you have, is the one I >>need. > >Thanks for that PS. I build the glibc libraries on RedHat 5.0 (albeit >updated to current releases of the kernel and other security/bug fixes) > >What happens if you just type "java -version" or "javac" > >The first should give you the version of the java system you are running >and the second should output the compiler options. If this does not >happen, try doing "which java" or "which javac" to find out where things >may be coming from. > > >Michael Sinz -- Director of Research & Development, NextBus Inc. >mailto:[EMAIL PROTECTED] --------- http://www.nextbus.com >My place on the web ---> http://www.users.fast.net/~michael_sinz > > > >
