testsuite says objects "are the same file"

Mon Mar 19 10:09:00 GMT 2001

I'm looking at the libjava testsuite and seeing a lot of messages like
spawn /home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/../libtool --silent --tag=GCJ --mode=compile /home/bothner/GNU/linux-gcc3/gcc/gcj -B/home/bothner/GNU/linux-gcc3/gcc/ -B/home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/../ -c -g -o /home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/G19990217_02.o /home/bothner/GNU/gcc3/libjava/testsuite/libjava.compile/G19990217_02.java 
mv: `G19990217_02.o' and `/home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/G19990217_02.o' are the same file
compiler exited with status 1
output is:
mv: `G19990217_02.o' and `/home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/G19990217_02.o' are the same file
FAIL: G19990217_02 compilation from source
PASS: G19990217_02 byte compilation
The same happens when I run libtool manually:
kelso<1821>pwd
/home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite
kelso<1822>/home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/../libtool --silent --tag=GCJ --mode=compile /home/bothner/GNU/linux-gcc3/gcc/gcj -B/home/bothner/GNU/linux-gcc3/gcc/ -B/home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/../ -c -g -o /home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/G19990217_02.o /home/bothner/GNU/gcc3/libjava/testsuite/libjava.compile/G19990217_02.java 
mv: `G19990217_02.o' and `/home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/G19990217_02.o' are the same file
But not when I run gcj directly:
kelso<1823>/home/bothner/GNU/linux-gcc3/gcc/gcj -B/home/bothner/GNU/linux-gcc3/gcc/ -B/home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/../ -c -g -o /home/bothner/GNU/linux-gcc3/i686-pc-linux-gnu/libjava/testsuite/G19990217_02.o /home/bothner/GNU/gcc3/libjava/testsuite/libjava.compile/G19990217_02.java
Is anyone else seeing this? A very quick look back at the archives
fails to find a similar report.
One mystery is why libtool thinks it needs to mv the .o file at all,
give that gcc does support -c combined with -o.
-- 
	--Per Bothner
per@bothner.com http://www.bothner.com/~per/