Mark Wielaard writes: > Hi Andrew, > > On Sat, 2006-12-16 at 17:37 +0000, Andrew Haley wrote: > > > OK. But I assume you do the second pass in some libgcj specific > > > Makefile. Can't you create the list there? > > > > I need to know which source files went into making the jar. How am I > > to know that? I just use Classpath's makefile. When I'm building > > libgcj, I get the list of source files from classpath/lib/classes. > > > > > > We need the full source pathnames for gcj to create correct debug > > > > information. We use the file classpath/lib/classes to so this for the > > > > main jarfile. You don't delete that file > > > > > > I believe we do. It is in the CLEANFILES like other generated files. > > > > Surely CLEANFILES are not deleted 'til 'make clean'. Can't > > all-classes.lst be added to CLEANFILES? > > Aha. OK. We don't need to clean the .lst files eagerly. Having them > removed in the clean target is enough. Done with the following patch:
Thanks. This removes a gcj divergence. Andrew.
