X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <06c301c7b4ad$ba1e0560$2e08a8c0@CAM.ARTIMI.COM> <20070622175610.GB15817@suncomp1.spk.agilent.com> Subject: RE: Help compiling gcc 4.2.0 Date: Sun, 24 Jun 2007 01:03:40 +0100 Message-ID: <078a01c7b5f3$1ef065a0$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20070622175610.GB15817@suncomp1.spk.agilent.com> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 22 June 2007 18:56, Gary Johnson wrote: > On 2007-06-22, Dave Korn wrote: >> On 21 June 2007 21:47, Lee Rhodes wrote: >> >> >>> I am struggling with the infamous unix/dos end-of-line '\r\n' vs '\n' >>> incompatibilities. It seems that no matter what shell I use (bash, sh, >>> Cygwin, rxvt, dos) that the gnu make utility throws errors when it sees >>> the '\r' CR character. >>> >>> Do I have to convert ALL the downloaded files into the unix format >>> (dos2unix)? >> >> Nope, what you have to do is you have to /not/ use winzip to unpack the >> archives. Use cygwin's command-line tar utility. > > I agree with the advice to use tar, but WinZip does have an option > to fix this behavior. It still won't get links and perms right, though. Don't use winzip. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/