From: "Ed Manlove" <emanlove AT ieee DOT org>
Newsgroups: comp.os.msdos.djgpp
References: <KFDW8.388$Si7 DOT 357662829 AT news DOT netcarrier DOT net> <7263-Wed10Jul2002080530+0300-eliz AT is DOT elta DOT co DOT il>
Subject: Re: patch and LFN support
Lines: 33
X-Newsreader: Microsoft Outlook Express 5.00.2615.200
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2615.200
Message-ID: <9qVW8.396$vo.361537634@news.netcarrier.net>
Date: Wed, 10 Jul 2002 08:01:03 -0400
NNTP-Posting-Host: 207.207.250.148
X-Complaints-To: news AT netcarrier DOT com
X-Trace: news.netcarrier.net 1026302725 207.207.250.148 (Wed, 10 Jul 2002 08:05:25 EDT)
NNTP-Posting-Date: Wed, 10 Jul 2002 08:05:25 EDT
Organization: NetCarrier Internet Services
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Thanks Martin and Eli again for your suggestions.  The -p0 option jumped
that hurdle.  The file names are identical but I believe this was
intentional in modifying the gcc cross compiler for specific LEGO MindStorms
RCX code.

Ed

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote in message
news:7263-Wed10Jul2002080530+0300-eliz AT is DOT elta DOT co DOT il...
> > From: "Ed Manlove" <emanlove AT ieee DOT org>
> > Newsgroups: comp.os.msdos.djgpp
> > Date: Tue, 9 Jul 2002 11:46:48 -0400
> >
> > ****************************************************** bash output
> > Tue Jul 9 10:40:16 2002 GCC patch start
> > Hmm...  Looks like a unified diff to me...
> > can't find file to patch at input line 3
> > Perhaps you should have used the -p or --strip option?
> > The text leading up to this was:
> > --------------------------
> > |--- gcc\config\h8300\h8300.c.orig      Thu Apr  8 01:17:52 1999
> > |+++ gcc\config\h8300\h8300.c.orig      Wed Aug 16 16:57:10 2000
> > --------------------------
> > File to patch:
>
> Try adding -p0 (that's a zero, not a letter `o') to the Patch command
> line, and make sure your current directory is the parent of the `gcc'
> directory under which there's config/h8300.c
>
> Also, note that the two files specified in the patch header have
> identical names, which might be another part of your problem.