From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28676 invoked by alias); 13 Nov 2002 19:59:30 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 28664 invoked from network); 13 Nov 2002 19:59:28 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 13 Nov 2002 19:59:28 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id gADJaFw06371 for ; Wed, 13 Nov 2002 14:36:15 -0500 Received: from hypatia.brisbane.redhat.com (IDENT:root@hypatia.brisbane.redhat.com [172.16.5.3]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gADJxJD07262 for ; Wed, 13 Nov 2002 14:59:20 -0500 Received: from scooby.brisbane.redhat.com (scooby.brisbane.redhat.com [172.16.5.228]) by hypatia.brisbane.redhat.com (8.11.6/8.11.6) with ESMTP id gADJweZ01685 for ; Thu, 14 Nov 2002 05:58:51 +1000 Received: by scooby.brisbane.redhat.com (Postfix, from userid 500) id 20AEE10A9F; Thu, 14 Nov 2002 06:58:27 +1100 (EST) Newsgroups: gmane.comp.gdb.devel Cc: sid@sources.redhat.com Subject: Re: SID compilation FAIL on alphaev56 References: <3DD2A669.87669C32@iol.unh.edu> Content-Type: text/plain; charset=US-ASCII From: Ben Elliston Date: Wed, 13 Nov 2002 11:59:00 -0000 Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley) In-Reply-To: bemis's message of "Wed, 13 Nov 2002 15:22:17 -0400" MIME-Version: 1.0 Posted-To: gmane.comp.gdb.devel X-SW-Source: 2002-q4/txt/msg00016.txt.bz2 The following message is a courtesy copy of an article that has been posted to gmane.comp.gdb.devel as well. >>>>> "bemis" == bemis writes: bemis> Is anyone currently working on sid? SID is causing our bemis> toolchain build to fail. I've read about this happening on bemis> systems other than alpha in the past. Is their a know patch bemis> for this? There were some C++ compliance patches committed this week. You could try getting a fresh update to see if the problems go away. Ben PS: You should post messages about SID to sid@sources.redhat.com.