Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <004501c13606$8f1bc4f0$af66323f@amr.corp.intel.com> From: "Tim Prince" To: , "Chris Faylor" References: <000a01bfaacd$ed1be870$b021e396 AT lin DOT foa DOT se> <001501bfac80$3a3338d0$0100000a AT TIMYX18EWDT6RQ> <8eaavo$i0m$1 AT cronkite DOT cygnus DOT com> Subject: Re: Can't build egcs-20000417 with cygwin-1.1.0 Date: Wed, 5 Sep 2001 05:30:31 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 As you can see from the version number, this is a long forgotten problem, corrected somewhere around cygwin-1.1.8. ----- Original Message ----- From: "Chris Faylor" Newsgroups: cygnus.egcs To: Sent: Thursday, April 27, 2000 2:20 PM Subject: Re: Can't build egcs-20000417 with cygwin-1.1.0 > In article <001501bfac80$3a3338d0$0100000a AT TIMYX18EWDT6RQ>, > Tim Prince wrote: > >As you may have noticed, I was able to build egcs-20000417 under > >cygwin-1.1.0 with exactly the same minor patches as under last summer's > >cygwin. Now that Chuck Wilson has corrected texinfo, it may even be > >possible to install the .info files, if you can get around all the > >problems with mixtures of line termination styles in the .texi files. > >However, with the increasing frequency of ICE's in the cygwin > >snapshots, which are more than enough to prevent running testsuite on > >g++, these attempts to use snapshot versions are looking less worth > >while. I suspect that many of the additional testsuite failures found > >with the new cygwin dejagnu are for real. > > Can you clue me in on these "ICE"s you're seeing with cygwin snapshots? > I assume that you're referring to problems with cygwin itself and not > gcc and this is the first I've heard of any problems. > > Obviously, I want to fix cygwin problems but I won't be able to do that > if I am completely unaware of the problems. > > cgf > -- > cgf AT cygnus DOT com Cygnus Solutions, a Red Hat company > http://sourceware.cygnus.com/ http://www.redhat.com/ > -- 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/