FYI: cause of fastjar failures in build

[Jerry Quinn <jlquinn at optonline dot net>]

I wrote at one point that I was having trouble during builds that looked like 
the following:

/home/jlquinn/gcc/dev/build/gcc/gcj 
-B/home/jlquinn/gcc/dev/build/i686-pc-linux-gnu/libjava/ 
-B/home/jlquinn/gcc/dev/build/gcc/ --encoding=UTF-8 -Wno-deprecated -C -g 
-classpath '' -bootclasspath 
/home/jlquinn/gcc/dev/build/i686-pc-linux-gnu/libjava:../../../gcc/libjava -d 
/home/jlquinn/gcc/dev/build/i686-pc-linux-gnu/libjava 
../../../gcc/libjava/org/w3c/dom/traversal/TreeWalker.java
find java gnu javax org -type d -o -type f -name '*.class' | \
  sed -e '/\/\./d' -e '/\/xlib/d' | \
  ../../fastjar/jar cfM0E@ libgcj-4.0.0.jar
/bin/sh: line 1: ../../fastjar/jar: No such file or directory
make: *** [libgcj-4.0.0.jar] Error 127

It turns out this is caused by class files in the source directories.  I've 
been using Eclipse to do some code editing and compile checking.  Eclipse 
leaves class files in the directory containing java files.  When you try to 
biuld the gcj libs, the build gets confused and the above error occurs.

The quick solution is to blow away any class files in the source directories 
java, javax, gnu, and org.

Is it worth trying to get the makefiles to detect and fix or work around this?

Thanks,
Jerry Quinn