Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!!FAHNOE, From: FAHNOE@UWPLATT.EDU (Larry Fahnoe, Coordinator of University Computing) Newsgroups: bit.listserv.pmdf-l Subject: Applying PMDF patches Message-ID: Date: 13 Feb 90 23:27:00 GMT Sender: PMDF Distribution List Reply-To: PMDF Distribution List Lines: 33 Approved: NETNEWS@PSUVM.BITNET Gateway Errors-to: postmast@YMIR.BITNET X-Organization: University of Wisconsin--Platteville X-Envelope-to: PMDF-L@IRLEARN.BITNET X-VMS-To: IN%"info-pmdf@ymir.claremont.edu" X-To: info-pmdf@YMIR Hello, In the applying patches to PMDF, I am confused as to how to use MAKE such that I can rebuild only those segments that need it. Specific example: Apply patch 3.1-6 to OS.PAS (edit file) $ make/keep/noexecute/out=build_os.com [src]makefile. [src]os.pas All targets in synch. (or a message quite close to that) and no .COM file is built. I've not used MAKE before (this may be obvious from the question) and my basic understanding is that I can use it to rebuild only those parts that need it. I wanted to produce a .COM file so I could see what was what before anything was done. PMDF 3.1-1 was installed on 19-Dec-1989, and I hand patched up through 3.1-5 today; in other words, the file mod dates should trigger the rebuild. Is it possible that since I recompiled BN_MASTER and PMDF_MAIL today that the dependency mechanism is confused? System is VMS 5.2. Any clues? Did I give enough information? In attempting to avoid the RTFM response, I did skim the MAKE.HLP file, but found little that shed light on this problem. --Larry Larry Fahnoe University Computing 608/342-1697 UW-Platteville BITNET: FAHNOE@UWPLATT One University Plaza Internet: FAHNOE@UWPLATT.EDU Platteville, WI 53181