Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!BBN.COM!jjd
From: jjd@BBN.COM (James J Dempsey)
Newsgroups: gnu.gcc.bug
Subject: gcc -o option, .o suffix
Message-ID: <8906131735.AA00348@life.ai.mit.edu>
Date: 13 Jun 89 17:28:20 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 28

I'm using gcc version 1.35 under Ultrix 3.0 on a Vax 8530.

I'm not on bug-gcc.

The standard "cc" found on ultrix will not allow you to use the -o
option with an argument that has a .o suffix.  This includes when you
use the -c option at the same time. This seems overly facist.

gcc will allow you to use the -o option with a .o suffix all the time.
If you specify an output file with the same name as your .c file but
with a .o suffix instead of .c, and you aren't using -c, then your
compile will always fail because ld will overwrite the object file.
This seems overly liberal.

In summary:

Not allowed by cc:
   cc foo.c -c -o foo.o         ; should be allowed

Allowed by gcc:
   cc foo.c -c -o foo.o         ;good
   cc foo.c -o bar.o            ;ok
   cc foo.c -o foo.o            ;probably shouldn't be allowed

		--Jim Dempsey--
		BBN Communications
		jjd@bbn.com (ARPA Internet)
                ..!{decvax, harvard, wjh12, linus}!bbn!jjd