naming conflicts in libgcj.a

Mon Jan 14 09:33:00 GMT 2002

There are several files within libgcj.a that have the same name (ie
Attributes.o). While this is technically allowed, it causes some tools
to choke (notably objcopy).
What do you all think about renaming .o's upon addition to the .a
archive? So Attributes.o would be added as "org.xml.sax.Attributes.o".
Are there any platforms that arbitrarily restrict the length of
ar-entry names? Even so, they're going to present a problem anyways
given Sun's habit of UsingReallyLongClassNamesInTheJava2API.
If this is reasonable I'll submit a patch.
 - a