Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 3 Dec 2002 12:17:50 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Resolved Re: gcc-3.2-1/i686-pc-cygwin/gcc/genflags is segfaulting Message-ID: <20021203171750.GC3443@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1038913777 DOT 10958 DOT 32 DOT camel AT lifelesswks> <20021203115206 DOT 10396 DOT qmail AT web13310 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021203115206.10396.qmail@web13310.mail.yahoo.com> User-Agent: Mutt/1.5.1i On Tue, Dec 03, 2002 at 03:52:06AM -0800, James Michael DuPont wrote: >Maybe this should be a release criterion? Not interested. Sorry. >Maybe you don't care if the gcc is fully usable before it is release? GCC *is* fully usable. If you can't build it, use the gcc binary that is provided. As you've probably surmised, I don't have the time or inclination to help other people try to figure out how to build gcc. I have no idea why it would be segfaulting or how to fix it. I suggest debugging the problem in gdb and offering solutions to the appropriate mailing list, which would be the gcc or gcc-patches mailing list in this case. cgf -- Please do not send me personal email with cygwin questions or observations. Use the resources at http://cygwin.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/