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
To: cygwin AT sourceware DOT cygnus DOT com
Subject: patch(1) can't patch files
From: Florian Weimer <fw AT deneb DOT cygnus DOT argh DOT org>
Date: 18 Sep 1999 18:08:53 +0200
Message-ID: <87yae4gq22.fsf@deneb.cygnus.argh.org>
Lines: 17
User-Agent: Gnus/5.070096 (Pterodactyl Gnus v0.96) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

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