X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Grant Edwards Subject: Re: gcc 3.4.4 crashing with segfault Date: Tue, 6 Jan 2009 00:22:56 +0000 (UTC) Lines: 21 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: slrn/pre0.9.9-102 (Linux) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 2009-01-05, Grant Edwards wrote: > While trying to build a gcc 3.2.1 cross-compiler on a current > Cygwin install, I get a repeatable segfault/internal-error from > gcc 3.4.4 [see below]. Just to reiterate: I mis-interpreted the error message. It's not the 3.4.4 native Cygwin compiler that's segfaulting. What's segfaulting is the 3.2.1 arm-elf targeted cross-compiler that has just been build and is then being used to build stdc++ libraries. I'm going to use the Cygwin time machine to go back in time a year or two at a time to see if I can find a point where the cross-compiler starts to work... -- Grant Edwards grante Yow! Like I always say at -- nothing can beat visi.com the BRATWURST here in DUSSELDORF!! -- 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/