Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!wuarchive!udel!mmdf From: EPRF%SNYCENVM.BITNET@cornellc.cit.cornell.edu (Peter Flass) Newsgroups: comp.os.minix Subject: Re: 1.1 -> 1.2 Patch Problems Message-ID: <7322@nigel.udel.EDU> Date: 3 Jan 90 18:32:43 GMT Sender: mmdf@udel.EDU Lines: 96 On Thu, 21 Dec 89 07:30:00 GMT Paul Allen said: >In article <3013@plains.UUCP> overby@plains.UUCP (Glen Overby) writes: >>In article <6465@nigel.udel.EDU> EPRF%SNYCENVM.BITNET@cornellc.cit.cornell.edu > (Peter Flass) writes: >>>On Fri, 15 Dec 89 22:02:50 GMT Scott A. Jordahl said: >> >>Summary: patch goes into a loop on the 1.1-1.2 upgrade kit from >> vm1.nodak.edu and starts acting weird. Patch -l doesn't help, >> either. >> >>Has anybody had a similar problem with a kit FTPed directly from bugs? > >I upgraded using the 1.2 and 1.3 upgrade kits on bugs, but I did all my >un-sharing and patching on a Sun. (My Minix machine at the time was the >two-floppy IPC card in my Sun.) I don't remember having any particular >trouble with the patches. > >Could this be a stack-size problem? Perhaps the original poster could >do a > > chmem =64000 patch > >and report back on what happens? > Here is a log and some relevant information on my problem patching CC.C from 1.2 -> 1.3. Another possibility is that there is a problem with my copy of cc. - Pete -------------- stuff follows -------------------------------------- >> Status of "Patch" text data bss stack memory 25840 5894 4842 54800 91376 /usr/bin/patch $Header: patch.c,v 2.0.1.5 88/06/03 15:09:37 lwall Locked $ Patch level: 11 >> Log from patch of 1.2 cc.c using patches from VM1.NODAK.EDU >> Command "patch -l&1 | tee patch.log Hmm... Looks like a context diff to me... The text leading up to this was: -------------------------- |diff -rc2 v1.2base/minix/commands/cc.c v1.3d/minix/commands/cc.c |*** v1.2base/minix/commands/cc.c Thu Sep 29 10:04:16 1988 |--- v1.3d/minix/commands/cc.c Thu Sep 29 21:47:47 1988 -------------------------- Patching file cc.c using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 1. Hunk #3 succeeded at 25. (Fascinating--this is really a new-style context diff but without the telltale extra asterisks on the *** line that usually indicate the new style...) Hunk #4 succeeded at 37. Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- | }; | | | #ifdef MEM640K -------------------------- Patching file cc.c using Plan A... (Fascinating--this is really a new-style context diff but without the telltale extra asterisks on the *** line that usually indicate the new style...) Hunk #1 succeeded at 35 with fuzz 1 (offset -3 lines). Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- | | | #ifdef MEM640K | /* MINIX paths for 640K PC (not 512K AT) */ -------------------------- Patching file cc.c using Plan A... Hunk #1 succeeded at 50 (offset 5 lines). Hunk #2 succeeded at 46 (offset -11 lines). Hunk #3 succeeded at 67 (offset 5 lines). Hunk #4 succeeded at 63 (offset -11 lines). Hunk #5 succeeded at 90 (offset 5 lines). +---------------------------------------------------------------------------+ | | | Peter Flass BITNET: EPRF@SNYCENVM (preferred) | | Director of Computing Services INTERNET: ESCFLASS@UBVM.CC.BUFFALO.EDU | | SUNY Empire State College AT&TNET: (518)587-2100 X350 | | 2 Union Avenue "After three days without programming, | | Saratoga Springs NY 12866 Life becomes meaningless" | | - The Tao of Programming | +---------------------------------------------------------------------------+