Date:	Thu, 6 Mar 1997 16:55:58 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Andy Eskilsson <x-aes AT telelogic DOT se>
cc:	djgpp AT delorie DOT com
Subject:	Re: Weird patch and redir problems.. Patch doesn't want to patch :-(
In-Reply-To:	<kswwrl9vua.fsf@telelogic.se>
Message-ID:	<Pine.SUN.3.91.970306164141.21561A-100000@is>
MIME-Version:	1.0

On 6 Mar 1997, Andy Eskilsson wrote:

> Patching file mm using Plan A...
> Hunk #1 succeeded at 1.
> Can't backup mm, output is in c:/temp/poaaaaaa: No such file or directory (ENOENT)
> done

Do you set LFN=y?  If not, set it and try again.  If you do have LFN=y, 
set it to n and see if that helps.  Methinks this is some kind of LFN 
mishap.

> d:\tst>redir -eo patch -p2 < diffs-t6 > outfile
> d:\tst>cat diffs-t6 | redir -eo patch -p2 > outfile
> 
> Tells me tht 4dos has performed an illegal operation and will be
> terminated.. unspecified exception, fault location 0000:00E.

Why are you trying to live dangerously?  Just let `redir' handle the
entire redirecting job, instead of relying on 4DOS: 

	redir -i diffs-t6 -o outfile -eo patch -p2

If this works, then both `redir' and `patch' live together in perfect 
harmony.

Explanation for the curious: when you use redirection symbols on the
command line, they actually redirect the input and output of `redir', not
of the program that `redir' runs.  You then rely on the intricacies (and
bugs) of the shell you use regarding the inheritance of the redirected
streams to child programs.  While this might well be a subject for a
post-doctorate, if you only need to make the damn thing work, I suggest to
stay away of this mess. 

> d:/tst: ls -l h:/djgpp/bin/patch.exe
> -rwxr-xr-x   1 flognat  dos        117248 Oct 19 11:28 h:/djgpp/bin/patch.exe*
> No more patch.exe found in the vicinity.. 

This is indeed the latest version.  I use it also.

- Raw text -