[-CURRENT tinderbox] failure on sparc64/sparc64

Harti Brandt brandt at fokus.fraunhofer.de
Tue Jul 15 12:40:29 PDT 2003

On Tue, 15 Jul 2003, Thomas Moestl wrote:

TM>On Tue, 2003/07/15 at 12:04:56 -0700, Marcel Moolenaar wrote:
TM>> On Tue, Jul 15, 2003 at 09:00:17PM +0200, Dag-Erling Sm?rgrav wrote:
TM>> > Marcel Moolenaar <marcel at xcllnt.net> writes:
TM>> > > It needs to be analyzed because cross-builds should not fail. Do
TM>> > > we have a machine problem? What exactly is dumping core? Is it
TM>> > > gzip or some binary started immediately after it? If it's gzip,
TM>> > > is there a relation with the recent compiler warning about strncmp?
TM>> >
TM>> > It's not a machine problem if it only happens to the sparc64 build -
TM>> > the same machine runs all the other -CURRENT tinderboxen except
TM>> > powerpc.
TM>> It does not only happen to sparc64. I've seen it fail for all but
TM>> i386 and pc98, I think.
TM>i386 and pc98 have failed too (random example: July 5).

But sparc64 fails quite regularily when gziping man pages. The others are
more random.

Since about the same time I have dumping core make during make universe on
my i386. The core shows differnt signals (4, 10, even SIGILL), but always
in vfork().

harti brandt,
brandt at fokus.fraunhofer.de, harti at freebsd.org

More information about the freebsd-current mailing list