On Tue, 2005-12-13 at 11:41 -0700, Tom Tromey wrote: > First, yeah, this is known. And, kudos to HJ for trying to fix this > in 'make'. If nothing else, HJ's hack is keeping things from being too insane while y'all sort out the best fix.
> I've been considering working around this problem by just redoing the > whole .java->.class step whenever any .java file changes. That would > probably be slower for libgcj developers but at least wouldn't hugely > hurt folks working elsewhere. Also, most class library development > happens in Classpath these days anyway. > > Any comments on this? No strong opinions on how you fix it, so long as it gets fixed :-) Waiting on this is a major time sink right now. In fact, this may be one of those cases where it's advisable to fix make *and* fix the Java runtime build stuff. jef
