Date: Tue, 15 Jul 2003 11:54:38 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Dag-Erling Sm?rgrav <des@des.no> Cc: sparc64@freebsd.org Subject: Re: [-CURRENT tinderbox] failure on sparc64/sparc64 Message-ID: <20030715185438.GB15674@dhcp01.pn.xcllnt.net> In-Reply-To: <xzp65m3vfw1.fsf@dwp.des.no> References: <200307141153.h6EBrJKk045346@cueball.rtp.FreeBSD.org> <20030715175821.K34004@beagle.fokus.fraunhofer.de> <xzp65m3vfw1.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 15, 2003 at 07:50:06PM +0200, Dag-Erling Sm?rgrav wrote: > Harti Brandt <brandt@fokus.fraunhofer.de> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715185438.GB15674>