libtool vs gcj

Richard Henderson rth@redhat.com
Mon Jan 15 17:13:00 GMT 2001


In testing libjava, I see lots of failures like

Executing on host: /bcpl/int/rth/egcs/build/x86/i686-pc-linux-gnu/libjava/testsuite/../libtool --silent --tag=GCJ --mode=compile /bcpl/int/rth/egcs/build/x86/gcc/gcj -B/bcpl/int/rth/egcs/build/x86/gcc/ -B/bcpl/int/rth/egcs/build/x86/i686-pc-linux-gnu/libjava/testsuite/../   -c -g  -o /bcpl/int/rth/egcs/build/x86/i686-pc-linux-gnu/libjava/testsuite/G19990217_02.o /bcpl/int/rth/egcs/egcs/libjava/testsuite/libjava.compile/G19990217_02.java    (timeout = 300)
mv: `G19990217_02.o' and `/bcpl/int/rth/egcs/build/x86/i686-pc-linux-gnu/libjava/testsuite/G19990217_02.o' are the same file
compiler exited with status 1
 
This appears to be caused by the generated libtool script having
"compiler_c_o=no" in the gcj section.  This appears to be due to
trying to compile C with a Java compiler, noticing that it doesn't
work, and deciding that that means that -o is not supported.

Suggestions?


r~


More information about the Gcc-bugs mailing list