X-Spam-Check-By: sourceware.org Message-ID: <44951BEB.90501@gmail.com> Date: Sun, 18 Jun 2006 10:24:59 +0100 User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923) MIME-Version: 1.0 To: cygwin CC: M DOT Hessling AT qut DOT edu DOT au Subject: Re: sed: 4.1.5 breaks libtool generation References: <20060618121448 DOT CEG03949 AT mail-msgstore01 DOT qut DOT edu DOT au> In-Reply-To: <20060618121448.CEG03949@mail-msgstore01.qut.edu.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit From: Dave Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Just sending the OPs reply so that it is in the mailing list archive. Mark Hessling wrote: >>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? > > Yes it does. Thanks. I wasn't aware of mount features; I've just been using the default mounts; d: -> /cygdrive/d, etc. which are in binary mode. > > Cheers, Mark. -- 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/