If you don't have a previous incarnation of GCJ installed...

[Bryce McKinlay]

Zack Weinberg wrote:

> This causes ltconfig to conclude that no, gcj doesn't support -c with
> -o.  So libtool tries to work around that with mv.  That in turn
> causes ~500 spurious testsuite failures, because the mv from fileutils
> 4.0 rejects an attempt to move a file onto itself.
>
> Sticking -fclasspath=${srcdir} into $GCJ in configure.in isn't good
> enough, because gnu/classpath/Configuration.java doesn't exist yet,
> and it tries to read that.

Yeah. But this just means you need to "make install" before "make check",
right? Or is the problem affecting you elsewhere?

My preferred solution is for libtool to stop doing silly tests! (there has
never been a GCJ that doesn't support "-c -o"), but don't think Oliva liked
that idea. Ideally we could put a flag in ltcf-gcj.sh that tells it not to
bother, but I don't see an obvious way to do that with the current libtool.

regards

  [ bryce ]