As mentioned here:
gcj will fail if asked to compile a .jar that contains a given
.class twice. At the very least it should emit a better error
I think in general, if a .jar is valid for the VM, then we should do our best to
compile it without an error. So - we should just ignore (well, issue a warning
perhaps) duplicately-named class files in a jar.
I wonder why this check doesn't catch it (jcf-parse.c):
if (CLASS_PARSED_P (current_class))
/* FIXME - where was first time */
fatal_error ("reading class %s for the second time from %s",
IDENTIFIER_POINTER (DECL_NAME (TYPE_NAME (current_class))),
CLASS_PARSED_P (current_class) = 1;
Subject: Bug 20502
Module name: gcc
Changes by: email@example.com 2005-03-17 15:54:24
gcc/java : ChangeLog jcf-parse.c
2005-03-17 Bryce McKinlay <firstname.lastname@example.org>
* jcf-parse.c (duplicate_class_warning): New function.
(java_parse_file): Call duplicate_class_warning if
CLASS_FROM_CURRENTLY_COMPILED_P is already set.
(parse_zip_file_entries): Likewise. Also set