Date: Tue, 15 Jul 2003 21:35:18 +0200 From: Thomas Moestl <t.moestl@tu-bs.de> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: sparc64@freebsd.org Subject: Re: [-CURRENT tinderbox] failure on sparc64/sparc64 Message-ID: <20030715193518.GA1660@crow.dom2ip.de> In-Reply-To: <20030715190456.GC15674@dhcp01.pn.xcllnt.net> References: <200307141153.h6EBrJKk045346@cueball.rtp.FreeBSD.org> <20030715175821.K34004@beagle.fokus.fraunhofer.de> <xzp65m3vfw1.fsf@dwp.des.no> <20030715185438.GB15674@dhcp01.pn.xcllnt.net> <xzpy8yzty2m.fsf@dwp.des.no> <20030715190456.GC15674@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2003/07/15 at 12:04:56 -0700, Marcel Moolenaar wrote: > On Tue, Jul 15, 2003 at 09:00:17PM +0200, Dag-Erling Sm?rgrav wrote: > > 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. > > It does not only happen to sparc64. I've seen it fail for all but > i386 and pc98, I think. i386 and pc98 have failed too (random example: July 5). - Thomas -- Thomas Moestl <t.moestl@tu-bs.de> http://www.tu-bs.de/~y0015675/ <tmm@FreeBSD.org> http://people.FreeBSD.org/~tmm/ PGP fingerprint: 1C97 A604 2BD0 E492 51D0 9C0F 1FE6 4F1D 419C 776C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715193518.GA1660>