Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!purdue!i.cc.purdue.edu!h.cc.purdue.edu!s.cc.purdue.edu!dls
From: dls@s.cc.purdue.edu (David L Stevens)
Newsgroups: comp.bugs.4bsd
Subject: Re: Make(1) does not support file inclusion +Fix
Message-ID: <2478@s.cc.purdue.edu>
Date: 15 Mar 88 22:18:26 GMT
References: <739@elxsi.UUCP> <539@hscfvax.harvard.edu>
Reply-To: dls@s.cc.purdue.edu.UUCP (David L Stevens)
Organization: PUCC UNIX Group
Lines: 27


	You should also be aware that these changes (in an earlier version,
at least) disallow explicit rules for RCS files, as we use. This means that
Makefiles that work with the standard make(1) will generate an error and exit.
	The problem is (or was, at least) with using an explicit rule of the
form:

	${SRC}:
		co $@

	We do this (locally) for all of our Makefiles, rather than hack
make(1). We evaluated Charlie's make(1) and discovered that it generated
the error message:

<blotto> has RCS file and rules.

	Thus, Makefiles from other places that have explicit RCS rules would
require source changes and (worse) you cannot customize an RCS rule.

	I admit that I haven't tried the above on the posted diffs, but I
discussed the problem with Charlie at the time (over a year ago) and there
were some technical difficulties in making it do the "right" thing, which is
to use explicit rules when they are there and only use the implicit rules
when they aren't. I assume this incompatibility persists, but welcome someone
else to give the definitive word.
-- 
					+-DLS  (dls@s.cc.purdue.edu)