Sender:	nate AT cartsys DOT com
Message-ID:	<357F44D7.99B40DD1@cartsys.com>
Date:	Wed, 10 Jun 1998 19:45:43 -0700
From:	Nate Eldredge <nate AT cartsys DOT com>
MIME-Version:	1.0
To:	Neil Roy <nitehackr AT sprint DOT ca>
CC:	djgpp AT delorie DOT com
Subject:	Re: Allegro diff patch problem
References:	<357EC531 DOT AB373438 AT sprint DOT ca>

Neil Roy wrote:
> 
> I have been using allegro 3.0 with the newest gnu/djgpp compiler (2.8.1
> ?) and I tried patching Allegro's difmay30.diff and I got an error.  I
> followed instructions to the letter, I re-installed Allegro 3.0, then I
> unzipped DIFMAY30.ZIP to my DJGPP directory (using the -d option in
> pkunzip), everything went where it was supposed to, allegro installed
> fine (I have installed and used it just fine in the past, no problems
> worth mentioning)
> 
> Here is what the docs say to do:
> 
> You should be one level up from the Allegro directory (in the djgpp
> directory), then type:
> patch -p1 < difmay30.diff
> 
> I typed it and got this error:
> Error: Unable to open patch file (-p1) for reading
> 
> ...upon looking at the patch command I got this syntax:
> 
> patch [-u] diffile profile [patchedfile]
> 
> I though I might be using a different patch command, seeing as how i
> don't delete anything installed I checked my entire hard drive for
> another patch command... there was only one so I was using the right
> one.  

You don't say it was the DJGPP one, however, and that output looks
nothing like the output from DJGPP patch.  If it's not in \djgpp\bin or
equivalent, it's the wrong one. If it is, then it must be a *very* old
version. Get the newest from Simtelnet.

If it is the wrong one, get the DJGPP version from Simtelnet and make
sure \djgpp\bin precedes the location of the other `patch' in your PATH
statement.

-- 

Nate Eldredge
nate AT cartsys DOT com

- Raw text -