From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24803 invoked by alias); 26 Aug 2004 16:10:08 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24774 invoked from network); 26 Aug 2004 16:10:06 -0000 Received: from unknown (HELO NUTMEG.CAM.ARTIMI.COM) (217.40.111.177) by sourceware.org with SMTP; 26 Aug 2004 16:10:06 -0000 Received: from mace ([192.168.1.25]) by NUTMEG.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.0); Thu, 26 Aug 2004 17:07:29 +0100 From: "Dave Korn" To: "'Fabian Cenedese'" , Subject: RE: gdb and older cygwins Date: Thu, 26 Aug 2004 16:10:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <5.2.0.9.1.20040826163328.01d43c40@NT_SERVER> Message-ID: X-OriginalArrivalTime: 26 Aug 2004 16:07:29.0250 (UTC) FILETIME=[C94F1C20:01C48B86] X-SW-Source: 2004-08/txt/msg00391.txt.bz2 > -----Original Message----- > From: gdb-owner On Behalf Of Fabian Cenedese > Sent: 26 August 2004 15:58 > >> > PS: The other solution would be to fix the 2.95.3 source > about this > >> > CRLF bug. I looked into the gcc list but couldn't find > >> simple patches, > >> > I guess it needs a bigger change. If anyone has some hints > >> about it... > > > > My first hint is this: never use WinZIP to unpack a > tarball in a cygwin > >environment, because it does the wrong thing with soft-links > and it mangles > >all the line endings. Use "tar xfv" instead. > > > > [Did I guess correctly how you managed to get your gcc > sources mangled?] > > It depends. I use cygwin only to compile gcc/gdb+co. The > intended platform > to use them is Windows with cygwin.dll, not the whole Cygwin > system. So > the source files which gcc will need to cope with ARE Windows > text files. You have two misunderstandings here: #1. The cygwin dll is all you need to be using Cygwin; it's the dll that provides the posix environment, it's the dll that handles textmode-vs-binmode and line endian-ness issues. Windows-plus-cygwin-dll equals cygwin equals Unix style line-ends. #2. It doesn't matter what platform you want to compile on. The gcc sources come with Unix-style LF line ends. They are NOT Windows text files unless *you* have altered them. If they now have CRs in them, it was *you* who put them there, when you didn't need to do so, and if you hadn't done so, it would have compiled fine under 2.95.3 > The source files for gcc and gdb of course I didn't unpack > with Winzip, > and if it's only because it doesn't understand tar/gz/bzip2 :) It didn't understand bzip2 last time I checked, but it had no trouble whatsoever with either tar, gz, or .tar.gz. In fact some versions (v8 upward IIRC) even have an option to decide whether to mangle line-ends or not specifically when unpacking a tar file. > As I will use gcc and gdb from Windows (and not in Cygwin) I guess > this is no option for me. As I point out above, if the cygwin dll is involved, you *are* in Cygwin; what you are running is *not* a native windows app and will follow Cygwin's preferences for line-end style. cheers, DaveK -- Can't think of a witty .sigline today....