Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <013101c36669$10f49710$7c3d8751@starfruit>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>
References: <004501c3657f$289744c0$6b547ad5 AT starfruit> <20030818160041 DOT GB3101 AT cygbert DOT vinschen DOT de> <20030819112817 DOT GL3101 AT cygbert DOT vinschen DOT de>
Subject: Re: patch unusable to apply patches to binary files
Date: Tue, 19 Aug 2003 16:46:32 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

Corinna Vinschen wrote:
> On Mon, Aug 18, 2003 at 06:00:41PM +0200, Corinna Vinschen wrote:
>> On Mon, Aug 18, 2003 at 12:52:09PM +0100, Max Bowsher wrote:
>>> Because patch always reads its input in textmode, it cannot be used to
apply
>>> patches to binary files - e.g. gcc-core-3.3-3.3.1.diff, which updates
binary
>>> .gmo files.
>>
>> Bummer.  I guess I have to patch patch once more.  I'll recycle the
>> --binary option again for this kind of situation as soon as I find some
>> spare time to do that.
>
> I've uploaded a 1.5.2 test version of a new patch, 2.5.8-7.  It
> reenables --binary for reading on Cygwin.
> Please give it a try (*iff* you're using Cygwin 1.5.2).

Yes, that works, thanks.

I'd like to have a go at finding a way for patch to do the right thing
without --binary. It seems wrong that it should read in textmode when every
mount in the system is binary - can you point me to anything in the
archives? I searched, but found nothing more recent than 2000.

Also, it is very hard to see what Cygwin specific changes you have made to
patch. There is the ChangeLog, but there is no patch, and no way to
reconstruct the official source release. There is, in fact, no way to obtain
the unmodified source at all, as it has not been restored to alpha.gnu.org
since that machine was compromised.

I don't suppose you feel like going Method One or Method Two, do you?

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/