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: <3DB0B48A.CCCE6B8A@yahoo.com>
Date: Fri, 18 Oct 2002 21:25:30 -0400
From: CBFalconer <cbfalconer AT yahoo DOT com>
Reply-To: cbfalconer AT worldnet DOT att DOT net
Organization: Ched Research
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: <crlf> vs <lf> and use of diff
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have some makefiles used with DJGPP which perform regression and
portability tests on my software.  They check things by doing a
run and then executing "diff -q" between the captured run and a
saved version.  The tests are run by a .bat file, and want to also
be runnable by a shell script.

They don't work.  The saved versions have <crlf> line endings, and
the newly created files have <lf> endings.  I thought that diff
ignored these differences as long as the files were not binary (no
<nul>s).  The -a option makes no difference.  I don't want to
revise the saved files because that would foul their utility
elsewhere.

I am using diff 2.8 on DJGPP, diff 2.8.1 on Cygwin.  Is this a
porting bug or a GNU bug or neither, and is there a workaround.

I also thought that I had read somewhere that the cygwin libraries
generated <crlf> output lines, but it is obviously not so.

Yes, I have read the FAQ and the UG.  Maybe I missed something.

-- 
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
   Available for consulting/temporary embedded and systems.
   <http://cbfalconer.home.att.net>  USE worldnet address!


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/