From owner-freebsd-sparc64@FreeBSD.ORG Fri Feb 3 17:54:09 2006 Return-Path: X-Original-To: sparc64@freebsd.org Delivered-To: freebsd-sparc64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D4FB16A420; Fri, 3 Feb 2006 17:54:09 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1CCD43D45; Fri, 3 Feb 2006 17:54:08 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k13Hp6Zi097097; Fri, 3 Feb 2006 10:51:07 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 03 Feb 2006 10:51:06 -0700 (MST) Message-Id: <20060203.105106.41729362.imp@bsdimp.com> To: des@des.no From: Warner Losh In-Reply-To: <86irrwre3y.fsf@xps.des.no> References: <86fyn242w0.fsf@xps.des.no> <20060203090804.Q59587@beagle.kn.op.dlr.de> <86irrwre3y.fsf@xps.des.no> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 03 Feb 2006 10:51:10 -0700 (MST) Cc: src-committers@freebsd.org, stable@freebsd.org, sparc64@freebsd.org Subject: Re: [releng_6 tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2006 17:54:09 -0000 From: des@des.no (Dag-Erling Sm=F8rgrav) Subject: Re: [releng_6 tinderbox] failure on sparc64/sparc64 Date: Fri, 03 Feb 2006 10:22:25 +0100 > Harti Brandt writes: > > The interesting point is: why does it build on my real sparc (2-UII= CPUs, = > > 512MByte memory), but not on the tinderbox. Is there something abou= t the = > > crosscompiler that is different? > = > Different CFLAGS perhaps? These different CFLAGS have been a source of unending problems. I've broken the tinderbox build a couple of times when my LINT build worked w/o hassle. And I got grumped at it, even though I did everything right. Maybe we can build the interbox with a set of standard, well known flags? Warner