Re: Multiple file compilation patch

[Per Bothner <per at bothner dot com>]

Bryce McKinlay <bryce@albatross.co.nz> writes:

> There are many problems caused by the multiple-input-file compilation
> patch ;-(
>  ...
> Could we please revert to the old behaviour by default (on the branch,
> at least)?. It seems to me that this mode would be better as an
> option, at least until it works more reliably.
> 
> $ gcj -c at/dms/classfile/*.java

This case should work as a *multiple* compilations of a single .java
file each time, because there is no -o flag.  I.e jc1 should be
invoked once per .java file.  It seems to do so when I tried a test.

> ././at/dms/classfile/Data.java: In class `at.dms.classfile.Data':
> ././at/dms/classfile/Data.java: In method `(java.io.InputStream)':
> ././at/dms/classfile/Data.java:0: Undefined variable or class name:
> `this$0'.
>    <<file too short - unexpected EOF>>
>    ^
> 1 error
> 
> $ gcj -c at/dms/classfile/Data.java
> $

You might want to pass -v to gcj to see what is going on.  My guess
is that it is not Data.java that is failing but some other file
earlier alphabetically which then refers to the class Data.

If you can send me the application, I will try to take a look.
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/