Re: depcomp problem [Fwd: Trying to compile latest CVS on old SCO unixware 2]

[Tom Tromey]

>>>>> "Derek" == Derek R Price <dprice@collab.net> writes:

Derek> Sounds like this could be fixed in depcomp?

Maybe...

Stephen> I'm Trying to update an old SCO unixware 2 box...Currently I
Stephen> have CVS 1.10.8 there. (Yeah, shame on me)

Stephen> The cc's -o option refuses to overwrite existing .o files...:

Wow, this is lame!  I can't imagine why a compiler would do this.  Do
SCO hackers never run `make' to rebuild a project?

Stephen>         source='argmatch.c' object='argmatch.o' libtool=no \
Stephen>         depfile='.deps/argmatch.Po' tmpdepfile='.deps/argmatch.TPo' \
Stephen>         depmode=none /bin/sh ../depcomp \
Stephen>         cc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -I../src      -g -c -o
Stephen> argmatch.o `test -f argmatch.c || echo './'`argmatch.c
Stephen> UX:cc: ERROR: -o would overwrite argmatch.o

I want to know if this happens because argmatch.o already exists, or
if it is because the SCO `cc' doesn't like `-c' and `-o' together.

I want to make sure we really know what is going on.  Could you run a
test or two to make sure this is what is happening?

If it is we can add an `rm -f foo.o' to the build rule.  I would like
to avoid that if possible though.

Tom