Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: "Ian Puleston" To: "Cygwin" Subject: RE: Perl bug with DOS file line endings? Date: Thu, 11 Jan 2001 16:11:32 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 I've discovered that problem this doesn't happen if I specify the default file format to be Unix when I install perl. However, specifying that on a system that's using only DOS format files would seem somewhat counter-intuitive? I suspect that this is actually a bug and doing the above simply avoids it. Ian > I wrote: > > Perl 5.6.1-1 seems to get confused as to whether its processing a DOS or > Unix format file, depending on what shell it is run under. I'm using it in > Windows 2000 to process a DOS format source file with line endings 0D0A > (\r\n): > > When it is run directly from a DOS command prompt it works as expected and > produces an output file with line endings 0D0A. > > When it is run from either bash or make initiated from a DOS > command prompt, > then it produces an output file with line endings 0D0D0A > (\r\r\n). It seems > that in this case it thinks that it is processing a Unix file, > and has added > a 0D to change from the Unix 0A line ending to the DOS 0D0A. > > I'm using CygWin make 3.79-3 and bash 2.04-5. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple