From: "chris.danx" Newsgroups: comp.os.msdos.djgpp References: <2950-Wed11Jul2001185249+0300-eliz AT is DOT elta DOT co DOT il> Subject: Re: Question on GPP 2.8.1 and DJGPP Lines: 36 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: <___27.27447$B56.4729855@news2-win.server.ntlworld.com> Date: Wed, 11 Jul 2001 17:19:22 +0100 NNTP-Posting-Host: 213.104.120.3 X-Complaints-To: abuse AT ntlworld DOT com X-Trace: news2-win.server.ntlworld.com 994868282 213.104.120.3 (Wed, 11 Jul 2001 17:18:02 BST) NNTP-Posting-Date: Wed, 11 Jul 2001 17:18:02 BST Organization: ntlworld News Service To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > > > I think a much less painful way would be to edit the patch file, and > > > manuall modify the file names to their original long names. If done > > > carefully, this will produce a patch that will simply work with no fuss. > > > > I've modified some of the file names in the patch file, but with > > each file comes more hunks that don't work. > > Sorry, I don't understand this sentence. Could you give an example? I meant to say that when i ran patch with djgpp.diff, i got some hunks that were rejected. When i modified the file names, I got even more hunks rejected (about 10-30 and only modified 3 filenames in the patch file). Some of the hunks are applied to the file no problem, but for others it doesn't work. As an example i changed the string "configur.lan" to "configure.lang" and some of the hunks were applied, others could not be applied. Previously i'd had a look at the erroneuos sections of code and tried to see what had gone wrong, unfortunately the number of errors is rising and i'm unable to keep up. The curious thing is that the files must be able to be built, otherwise there would be no binary distribution. So by that logic, when i've modified the patch file to accomodate long filenames, it should build even if some hunks cannot be applied. Maybe I'm wrong, but I can't see any other explanation. > > I don't even know what a hunk > > A hunk is a fragment of the patch file which describes a change to a > contiguous range of source file lines. Each hunk begins with a header > that states the affected lines' numbers, and then the actual changed > lines. Thanks for explaining that to me, Chris Campbell