[Patch] ecj1 always fails with OpenJDK runtime.

[Andrew John Hughes]

2009/3/27 Andrew Haley <aph@redhat.com>:
> David Daney wrote:
>> When ecj1 is run using the OpenJDK runtime, gcj -C always exits with a
>> failure exit code (1) even though no diagnostics are issued.
>>
>> I tracked the problem down to a difference in behavior between the
>> libgcj and OpenJDK for java.util.ZipOutputStream.
>> org/eclipse/jdt/internal/compiler/batch/GCCMain tries to create a zip
>> stream with no files.  This succeeds under libgcj but fails under OpenJDK
>>
>> My hackish fix is to always create an empty file named '.dummy' in the
>> stream.  I don't know if this is completely safe, but it does allow me
>> to successfully do a --enable-java-maintainer-mode build.
>>
>> 2009-03-26  David Daney  <ddaney@caviumnetworks.com>
>>
>>     * org/eclipse/jdt/internal/compiler/batch/GCCMain.java (fail):
>>     print a stack trace.
>>     (getZipOutput,getDependencyOutput): Create an empty dummy entry.
>>
>
> I'm surprised I never saw this.  Andrew Overholt: where should this go?
>
> Andrew.
>

I'm surprised the difference between the two zip implementations
wasn't spotted, but I'm not surprised that ecj1 hasn't been run with
OpenJDK, given (at least as far I understand it), it's specific to the
GCJ frontend.
-- 
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8