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 Date: Tue, 31 Jul 2001 06:59:08 -0400 From: Christopher Faylor To: cygwin@cygwin.com, gcc@gnu.org Subject: Re: GCC 3.0 for i686-pc-cygwin target, bootstrap fails Message-ID: <20010731065908.A18833@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com, gcc@gnu.org References: <200107310454.VAA29823@famine.OCF.Berkeley.EDU> <0d4b01c11989$dbdfb650$2101bf0a@houston.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <0d4b01c11989$dbdfb650$2101bf0a@houston.rr.com>; from cjoy@houston.rr.com on Tue, Jul 31, 2001 at 01:27:20AM -0500 On Tue, Jul 31, 2001 at 01:27:20AM -0500, Corwin Joy wrote: > >----- Original Message ----- >From: "Di-an Jan" >To: ; >Cc: ; >Sent: Monday, July 30, 2001 11:54 PM >Subject: Re: GCC 3.0 for i686-pc-cygwin target, bootstrap fails > > >> > ../../gcc-3.0/gcc/config/i386/i386.md:289: unknown rtx >> > code 'define_asm_attributes >> ><...snip..> >> > Anyway, the problem seems to have something to do with carriage return >> > versus line-feed under Cygwin. ><...snip..> >> I ran into the same. The problem is that '\r' is not recognized as white >> space in various parts of "rtl.c". Specifically, "read_name" thinks '\r' >> is a part of the name. >> >> A better fix is probably to put the sources under a directory mounted >> textmode (or change the mount to binmode if the files are already >> extracted). If the directory is set for binmode, Cygwin's "tar" does not >> add extra '\r' but external programs such as WinZip might, and "rtl.c" >> don't handle it well enough. > >This would likely be what bit me. As someone more conversant with NT than >Cygwin I just used WinZip to uncompress the distribution file which may have >added the extra '\r'. > >> I think a note should be added to the "Host/target specific installation >> notes" page that either the sources should be extracted with Cygwin "tar" >> or extracted to a directory mounted textmode. >> >> A strong warning should also be added to the Cygwin User's Guide that >> binmode cannot maintain Unix newline conventions if non-Cygwin programs >> such as WinZip are used, and some programs will fail. So much for the idea of a "strong warning...[about] non-Cygwin programs". We already warn against using WinZip in the documentation but... cgf -- 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/