On Sat, 24 Nov 2001, John P. Verel wrote: > Right, my current directory is in my classpath for both machines. But > javac in windows sees the .java files and compiles them,, the Linux > javac does not. Your example below is consistent with mine on Linux. > Question why I get differing behavior on the windows machine.
I don't understand. My example below clearly shows linux compiling both files just fine if . is in the classpath (either specified on the command line, or through the env variable). > > John > On 11/24/01, 11:04:27PM -0500, [EMAIL PROTECTED] wrote: > > On Sat, 24 Nov 2001, John P. Verel wrote: > > > > > I may have not stated the question correctly. > > > > No, I understood. I may have not stated the answer clearly. > > > > > I have two files, foo1.java and foo2.java foo2.java imports foo1. On my > > > Windows machine, I can simply execute javac foo2.java and javac compiles > > > foo1.java and foo2.java. Same jdk on Linux does not. In neither case do I > > > have a classpath set. On my windows machine, I have a dot at the end of the > > > path search to denote the current address. I had expected the Linux version to > > > automatically find foo1.java compile it and import the class file into foo2, > > > but that is not happening. > > [cgalpin@kanga jdktest]$export CLASSPATH=. > > [cgalpin@kanga jdktest]$ rm *.class > > [cgalpin@kanga jdktest]$ javac foo2.java > > [cgalpin@kanga jdktest]$ java foo2 > > sit > > woof > > [cgalpin@kanga jdktest]$ This shows that foo1.class is also compiled and used when compiling/executing foo2 charles _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
