Path: utzoo!attcan!uunet!husc6!uwvax!tank!uxc!uxc.cso.uiuc.edu!m.cs.uiuc.edu!wsmith
From: wsmith@m.cs.uiuc.edu
Newsgroups: comp.lang.c
Subject: cc design flaw
Message-ID: <4700028@m.cs.uiuc.edu>
Date: 8 Nov 88 17:37:00 GMT
Lines: 18
Nf-ID: #N:m.cs.uiuc.edu:4700028:000:562
Nf-From: m.cs.uiuc.edu!wsmith    Nov  8 11:37:00 1988


The cc compiler in Berkeley unixes leaves .o files in the current
directory even when the source file is in different directory.

cc -c File/afile.c

will leave the .o file at ./afile.o

This makes it awkward to build a default .c.o rule for make that will behave
correctly when I have several versions of the same files in different sub-
directories.  Encore's Multimax make solves this problem, but since it is
an extension to make, the make files will not port to other machines.

Very annoying to say the least.

Bill Smith
uiucdcs!wsmith
wsmith@cs.uiuc.edu