From owner-freebsd-current@FreeBSD.ORG Fri Oct 26 19:08:33 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4A5A7D24; Fri, 26 Oct 2012 19:08:33 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id EFA0E8FC12; Fri, 26 Oct 2012 19:08:32 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id wc20so3800016obb.13 for ; Fri, 26 Oct 2012 12:08:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nbt/sT7f9UvKGDHpiuw3tA2RAiXXSSNKfhsnCHZTDlQ=; b=o8AyA5jWr/ZvCPBxEGbNiEfFOWwGDJGjCXuG6teSdc3y+UOuAqy3w4O5YjMmjKs9TJ U9zUu7GfqJL4oWcmAZ7MT4bp22BNxuDHJmLG6G6YOXtph01slcMc93n8Z1+RR0ugtO4m 7whDQ2H5/ZN1Ltaso1E7mfq2dOxYWkYMZK/62gFWiedLfuna8wtqOwp+cxMXgqM695v4 W5z47U0GNES+BdfFLPuMn5hPPtxHig2sPf3qUmW6XstduIMo+q8geDZi8tMZ+KuVDjGs o3v0YG6wR2p3++qzF7sVFS1arr6bms0rgDX79dVFEHahpgCvfwFYQ0CktvEwlusR1PY9 DcNQ== MIME-Version: 1.0 Received: by 10.60.169.170 with SMTP id af10mr20498282oec.17.1351278512493; Fri, 26 Oct 2012 12:08:32 -0700 (PDT) Received: by 10.76.143.33 with HTTP; Fri, 26 Oct 2012 12:08:32 -0700 (PDT) In-Reply-To: References: Date: Fri, 26 Oct 2012 12:08:32 -0700 Message-ID: Subject: Re: make tinderbox failures From: Garrett Cooper To: mdf@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org, Warner Losh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 19:08:33 -0000 On Fri, Oct 26, 2012 at 10:26 AM, wrote: > Running make tinderbox locally I see failures that aren't being > reported by the automated tinderbox builds. I'm curious what's > different about the environment. Failures are in the following: > > arm ARMADAXP kernel failed, check _.arm.ARMADAXP for details > mips SENTRY5 kernel failed, check _.mips.SENTRY5 for details > mips XLPN32 kernel failed, check _.mips.XLPN32 for details > mips XLR kernel failed, check _.mips.XLR for details > mips XLRN32 kernel failed, check _.mips.XLRN32 for details > > _.arm.ARMADAXP: > /data/sb/bsd.git/sys/arm/mv/armadaxp/armadaxp_mp.c: In function > 'platform_mp_start_ap': > /data/sb/bsd.git/sys/arm/mv/armadaxp/armadaxp_mp.c:181: warning: > passing argument 1 of 'pmap_kextract' makes integer from pointer > without a cast > > _.mips.SENTRY5: > config: Error: device "siba" is unknown > > _.mips.XLPN32 and _.mips.XLRN32: > linking kernel.debug > stack_machdep.o: In function `stack_capture': > /data/sb/bsd.git/sys/mips/mips/stack_machdep.c:(.text+0x34): undefined > reference to `stack_zero' > /data/sb/bsd.git/sys/mips/mips/stack_machdep.c:(.text+0x34): > relocation truncated to fit: R_MIPS_26 against `stack_zero' > /data/sb/bsd.git/sys/mips/mips/stack_machdep.c:(.text+0x13c): > undefined reference to `stack_put' > /data/sb/bsd.git/sys/mips/mips/stack_machdep.c:(.text+0x13c): > relocation truncated to fit: R_MIPS_26 against `stack_put' > > _.mips.XLR: > linking kernel.debug > board.o: In function `xlr_board_info_setup': > /data/sb/bsd.git/sys/mips/rmi/board.c:(.text+0x3a4): undefined > reference to `__ucmpdi2' > /data/sb/bsd.git/sys/mips/rmi/board.c:(.text+0x3a4): relocation > truncated to fit: R_MIPS_26 against `__ucmpdi2' > /data/sb/bsd.git/sys/mips/rmi/board.c:(.text+0x3e4): undefined > reference to `__ucmpdi2' > /data/sb/bsd.git/sys/mips/rmi/board.c:(.text+0x3e4): relocation > truncated to fit: R_MIPS_26 against `__ucmpdi2' > > Since I don't work on arm or mips I generally ignore these. But it > makes it harder to have confidence in a global change when make > tinderbox throws errors locally. These are probably due to the changes that Warner made recently to the mips conf files. Thanks, -Garrett