From owner-freebsd-sparc64@FreeBSD.ORG  Thu Jun 21 09:29:56 2012
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 89E011065675
	for <freebsd-sparc64@FreeBSD.org>; Thu, 21 Jun 2012 09:29:56 +0000 (UTC)
	(envelope-from gerald@pfeifer.com)
Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66])
	by mx1.freebsd.org (Postfix) with ESMTP id 66F1E8FC08
	for <freebsd-sparc64@FreeBSD.org>; Thu, 21 Jun 2012 09:29:56 +0000 (UTC)
Received: from [149.44.171.166] (charybdis-ext.suse.de [195.135.221.2])
	by ainaz.pair.com (Postfix) with ESMTPSA id 93A9F3F41B;
	Thu, 21 Jun 2012 05:29:49 -0400 (EDT)
Date: Thu, 21 Jun 2012 11:29:48 +0200 (CEST)
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Anton Shterenlikht <mexas@bristol.ac.uk>, freebsd-sparc64@FreeBSD.org
In-Reply-To: <20120621081705.GA41013@mech-cluster241.men.bris.ac.uk>
Message-ID: <alpine.LNX.2.00.1206211127380.3158@gerinyyl.fvgr>
References: <20120621081705.GA41013@mech-cluster241.men.bris.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 
Subject: Re: lang/gcc46 build failure on sparc64
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>, 
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 09:29:56 -0000

On Thu, 21 Jun 2012, Anton Shterenlikht wrote:
> Apologies if I have reported this already,
> I lost track with all the png- triggered updates.
> 
> On sparc64 10.0-CURRENT #4 r235474, updating from
> gcc-4.6.4.20120413 to gcc-4.6-20120608 I get: 

Do others see the same on sparc64?  I do not have access to such
a machine and this does not look like a SPARC-specific issue.

My money is on this being caused by something in the base.

Gerald