From owner-freebsd-sparc64@FreeBSD.ORG Tue Jul 15 11:54:56 2003 Return-Path: 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 1A24D37B419; Tue, 15 Jul 2003 11:54:56 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 095DD43F93; Tue, 15 Jul 2003 11:54:55 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6FIshv1098787; Tue, 15 Jul 2003 11:54:43 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6FIshNd015724; Tue, 15 Jul 2003 11:54:43 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h6FIsduO015723; Tue, 15 Jul 2003 11:54:39 -0700 (PDT) (envelope-from marcel) Date: Tue, 15 Jul 2003 11:54:38 -0700 From: Marcel Moolenaar To: Dag-Erling Sm?rgrav Message-ID: <20030715185438.GB15674@dhcp01.pn.xcllnt.net> References: <200307141153.h6EBrJKk045346@cueball.rtp.FreeBSD.org> <20030715175821.K34004@beagle.fokus.fraunhofer.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i cc: current@freebsd.org cc: sparc64@freebsd.org Subject: Re: [-CURRENT tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 18:54:56 -0000 On Tue, Jul 15, 2003 at 07:50:06PM +0200, Dag-Erling Sm?rgrav wrote: > Harti Brandt writes: > > Is there any specific reason that the sparc64 tinderbox permanently dumps > > core? I have no problem here to build world on my sparcs. > > Remember, this is a cross-build... It needs to be analyzed because cross-builds should not fail. Do we have a machine problem? What exactly is dumping core? Is it gzip or some binary started immediately after it? If it's gzip, is there a relation with the recent compiler warning about strncmp? In other words: what the fuck is going on and why doesn't anybody do something about it? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net