X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Where is patch?
Date: Thu, 15 Dec 2005 18:31:35 -0000
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <43A1B2A1.2020907@student.lu.se>
Message-ID: <SERRANO1RXRRbBtupMs00000045@SERRANO.CAM.ARTIMI.COM>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Lennart Borgman wrote:
> 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?

  Hooray!  Sounds like you've got it all sorted out now to me!  Two pieces of
advice:

1) You didn't say if you've run "make install" yet though, you should do that
rather than attempting to manually copy all the files to their correct
locations.

2) If you'd like to keep your original cygwin version of patch as well, just
in case your new one goes wrong, pass an option like "--prefix=/usr/local/" to
configure, then the binary (and all associated man/info pages, etc) get
installed into the tree under /usr/local, rather than overwriting the cygwin
package version under /usr.  Then you just need to make sure /usr/local/bin is
in your $PATH ahead of /bin and /usr/bin (which are secretly one and the same
behind the scenes).

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

  It sounds like it shouldn't be too hard.

> (But please no holy war on line end style. That is just
> improductive.)

  I fully agree!  Tools should be flexible and well written and deal
intelligently with any kind of line-end they are presented with.  We've had
over two decades to get used to these new-fangled CRLF endings, we should be
able to cope by now!  We must make computers do what their users want, not
expect users to fit themselves to suit the computer!

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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