Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Problems upgrading from 2.95.3-5 to 3.X on cygwin
Date: Sat, 2 Feb 2002 06:57:13 +0800
Message-ID: <8D00C32549556B4E977F81DBC24E985D410215@crtsmail1.technol_exch.corp.riotinto.org>
Thread-Topic: Problems upgrading from 2.95.3-5 to 3.X on cygwin
Thread-Index: AcGrbIxczNgUXNEYRhuZVjxn3axkfQABsMxg
From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
To: "Mack Lobell" <macklobell@hotmail.com>
Cc: <cygwin@cygwin.com>, <gcc@gcc.gnu.org>
Content-Transfer-Encoding: 8bit

Mack,

A couple of things to try:

Unpack the gcc source tree using cygwin tar and gzip/bzip2.  Some windows utilities are "smart" enough to convert \n to \r\n

Try using binary mounts for the source and build trees.

Use the configure options I posted earlier. 

-----Original Message-----
From: Neil Booth [mailto:neil@daikokuya.demon.co.uk]
Sent: Saturday, 2 February 2002 9:05 
To: Mack Lobell
Cc: cygwin@cygwin.com; gcc@gcc.gnu.org
Subject: Re: Problems upgrading from 2.95.3-5 to 3.X on cygwin


I suggest you remove all '\r' characters from i386.md, so that the
newlines consist of '\n' only.  That will likely solve your problem.

You needn't bother with insn-flags.h; that looks to be only a warning
and once you get stage1 built of 3.0, it won't have problems with
'\r' (but the .md file still might; I'm not sure about that).

Neil.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/