Jason,
Your path may still be the problem. Un*x doesn't search the current
directory unless the path contains a "." and, if the path does contain a
".", the current directory will be searched after any directories that
precede that "." in the path.
It sounds like you may be executing a different javac. Have you got kaffe
installed, by chance?
Douglas Toltzman
At 12:08 PM 10/15/98 -0700, Chambers Jason wrote:
>I picked up the following message from the mailing list:
>
>
>>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?
>
>
>I am having the exact same problem. I still haven't managed to solve
>it. If you have solved it by now, let
>me know. I heard a recommendation that a new version of
>glibc needs to be installed. I think its quite risky to
>blindly install such a fundamental library. I would much sooner
>install a patch if indeed this is the problem. Another thing that was
>recommended was that I remove the linux libraries from the green
>threads directory. I did this but still it didn't work. I figured the
>Java compiler might be missing a library, so I hacked the script to do
>an ldd on the actual executable - all libraries are found.
>
>I know of someone else who had this problem. Their solution was to
>revert back to JDK.1.1.5 but I don't want to do that.
>_________________________________________________________
>DO YOU YAHOO!?
>Get your free @yahoo.com address at http://mail.yahoo.com
>
