Date: Tue, 15 Jul 2003 21:00:17 +0200 From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) To: Marcel Moolenaar <marcel@xcllnt.net> Cc: sparc64@freebsd.org Subject: Re: [-CURRENT tinderbox] failure on sparc64/sparc64 Message-ID: <xzpy8yzty2m.fsf@dwp.des.no> In-Reply-To: <20030715185438.GB15674@dhcp01.pn.xcllnt.net> (Marcel Moolenaar's message of "Tue, 15 Jul 2003 11:54:38 -0700") References: <200307141153.h6EBrJKk045346@cueball.rtp.FreeBSD.org> <20030715175821.K34004@beagle.fokus.fraunhofer.de> <xzp65m3vfw1.fsf@dwp.des.no> <20030715185438.GB15674@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Moolenaar <marcel@xcllnt.net> writes: > 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? It's not a machine problem if it only happens to the sparc64 build - the same machine runs all the other -CURRENT tinderboxen except powerpc. There doesn't seem to be anything wrong with the sources either. There's not much more I can say about it until I see the full log from the next run; the last one broke at a different point. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpy8yzty2m.fsf>