X-Spam-Check-By: sourceware.org
Message-ID: <4493C7B4.4040107@gmail.com>
Date: Sat, 17 Jun 2006 10:13:24 +0100
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
MIME-Version: 1.0
To: M DOT Hessling AT qut DOT edu DOT au
CC: cygwin AT cygwin DOT com
Subject: Re: sed: 4.1.5 breaks libtool generation
References: <20060617142400 DOT CEF67313 AT mail-msgstore01 DOT qut DOT edu DOT au>
In-Reply-To: <20060617142400.CEF67313@mail-msgstore01.qut.edu.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
From: Dave <kilroyd AT googlemail DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Mark Hessling wrote:
>>Actually, what you describe is clear enough, but since CRLF handling
>>isn't done by the Linux version of sed either, you would have the same
>>problem on Linux.  The question here is how did this file get created
>>with CRLF in the first place?
> 
> I have several cross-platform projects managed in a CVS repository.  Several of them are built with different Win32 compilers on the same Windows XP machine.
> So my direcory tree looks something like:
> 
> projects
> Regina
>   vc
>   bcc
>   cygwin
> 
> Given the fact that cygwin runs on a machine where the native linend is CRLF, having a major component not recognise CRLF as a linend when handling text files is, AFAIAC, a major problem.

Given that you know all the files in this tree are CRLF terminated, is 
it appropriate to mount this directory in text mode?

Does the configure work if this is done?

Dave.

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