X-Spam-Check-By: sourceware.org
Message-ID: <43A1B2A1.2020907@student.lu.se>
Date: Thu, 15 Dec 2005 19:14:57 +0100
From: Lennart Borgman <lennart.borgman.073@student.lu.se>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
MIME-Version: 1.0
CC: Dave Korn <dave.korn@artimi.com>, cygwin@cygwin.com
Subject: Re: Where is patch?
References: <SERRANOMu3QTYCrtU2b00000042@SERRANO.CAM.ARTIMI.COM> <43A1ACC1.9090805@student.lu.se>
In-Reply-To: <43A1ACC1.9090805@student.lu.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Lennart Borgman wrote:

> Dave Korn wrote:
>
>> And the answer is that as is the GNU assembler, and it is part of the
>> binutils package, which lives under the 'Devel' category in setup.
>>  
>>
> Thanks for this! That trick is so handy in my opinion so it ought to 
> be as a tip on the search page right under the search box!

After finishing the installation of gcc-core (which includes binutils as 
far as I understand) configure + make ran fine. I have now patch 2.5.9 
compiled for Cygwin I believe. Or?

My intention was to look at the source code and see how it handles line 
endings. I do not know if that is realistic though. As I said before 
what I want it to do is:

1) Keep the line end style for the patched file.

2) Read the patch file and apply it even if it uses a different line end 
style.

This is simply what I expect of a text oriented tool. Comments and help 
are welcome! (But please no holy war on line end style. That is just 
improductive.)

--
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/

