Path: utzoo!attcan!uunet!husc6!rutgers!att!whuts!homxb!antique!cjp
From: cjp@antique.UUCP (Charles Poirier)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Manx make
Summary: Try using copy not cp
Message-ID: <2357@antique.UUCP>
Date: 28 Jul 88 02:30:51 GMT
References: <3047@tekig4.TEK.COM>
Reply-To: vax135!cjp (Charles Poirier)
Organization: AT&T Bell Labs, Holmdel, NJ
Lines: 29

In article <3047@tekig4.TEK.COM> brianr@tekig4.UUCP writes:
<----> begin makefile excerpt <-----
...
<$(OBJS):	ram:precompiled_include
<
<ram:precompiled_include:	precompiled_include
<	cp precompiled_include ram:
<#
<# Note use of `cp' instead of `copy'.
<#
<This gem behaves like `copy' SHOULD've, in that the copy's file
<creation date is set to the original's.
...
<*BUT*, if I immediately re-issue the `make' command, it will RE-COPY
<the `precompiled_include' file to ram:, and RE-COMPILE ALL THE MODULES,
<even though everything should be `up to date'.

Perhaps make is not satisfied that two dependent files have the
same exact age; it could want the dependent file to be strictly more
recent.  Thus, the ram:pre file is not up-to-date with respect to
disk:pre, and since $(OBJS) depend on the ram: file, they too are not
up-to-date.  Try this scheme with the regular "copy" which does not
preserve dates, and I bet it works fine.

	Charles Poirier
-- 
	Charles Poirier   (decvax,ucbvax,mcnc,attmail)!vax135!cjp

   "Docking complete...       Docking complete...       Docking complete..."