Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: "Suhaib M. Siddiqi" <ssiddiqi AT ipass DOT net>
To: "Florian Weimer" <fw AT deneb DOT cygnus DOT argh DOT org>,
        <cygwin AT sourceware DOT cygnus DOT com>
Subject: RE: patch(1) can't patch files
Date: Sat, 18 Sep 1999 12:42:08 -0400
Message-ID: <LOBBLPGIHMIEGBEAFDMCMEBDCBAA.ssiddiqi@ipass.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <87yae4gq22.fsf@deneb.cygnus.argh.org>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211

Yes, I observed that too, with patch.exe.  Also when applying large patches
, say 3 to 10 MB, patch.exe (from Cygwin and MingW32) did core dump.

However, you can grap a patch.exe from my URL
http://www.geocities.com/ResearchTriangle/Forum/6298

I modified the code, and compiled it with Microsoft Visual C++ (MSVC 6.0)
The modified code is included in the archive (Patch.zip).

Suhaib

> -----Original Message-----
> From: cygwin-owner AT sourceware DOT cygnus DOT com
> [mailto:cygwin-owner AT sourceware DOT cygnus DOT com]On Behalf Of Florian Weimer
> Sent: Saturday, September 18, 1999 12:09 PM
> To: cygwin AT sourceware DOT cygnus DOT com
> Subject: patch(1) can't patch files
> 
> 
> I've received a report that GNU patch doesn't work correctly under
> Cygwin-b20 if the directory for temporary files and the files to patch
> aren't on the same drive (this behavior was observed under Windows 95):
> 
> patch -p1 < gnus-0.95-0.96.diff 
> patching file `lisp/ChangeLog'
> patch: **** can't rename `C:\WINDOWS\TEMP/po001004' to
> `lisp/ChangeLog' : File exists
> 
> GNU patch contains its own implementation of rename() which uses hard
> links (at least on Unix) and a copy-and-delete fallback mechanism
> for cross-filesystem renames.  Obviously, this implementation of
> rename() expects certain error values from link() &c which the cygwin
> implementation doesn't provide.
> 
> (Unfortunately, I don't have working installation of cygwin-b20 myself,
> which means I can't give more information here or do additional testing.)
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com