Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: jbowe@pineapple.bbn.com (John Bowe)
Newsgroups: comp.sys.sun
Subject: Re: odd things defined in Sun make 4.0
Message-ID: <8902132215.AA08421@ugli.bbn.com>
Date: 22 Feb 89 18:42:48 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 21
Approved: Sun-Spots@rice.edu
Original-Date: Mon, 13 Feb 89 17:15:32 EST
X-Sun-Spots-Digest: Volume 7, Issue 166, message 2 of 15

mjr@cthulhu.welch.jhu.edu (Marcus J. Ranum):
> Is it normal for all makes to have a target coded into them for
> 'markfile.o', depending on 'markfile' and grabbing the sccsid from it ? 
> 
> I did a "make -p" the other day, and noticed this little hack, just
> waiting to bite someone.

This is also true of SunOS 3.[45].

Try this one (curtesy r$):
Create a file named "markfile" that has only RCS info and check it in
	% cat >markfile
	$Header:$
	$Log:$
	% ci markfile
now, with the sysV-derived MAKE, you'll automatically get a file that has
	static char _sccsid[] = "$Header: markfile r1.3, 10/10/89 ...";
as its only line, which you can compile and do an "ident" on to see the
revision.

	john	<jbowe@bbn.com>