From owner-freebsd-current@FreeBSD.ORG Fri Oct 26 17:26:55 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 EDBF4975 for ; Fri, 26 Oct 2012 17:26:55 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id C12408FC0A for ; Fri, 26 Oct 2012 17:26:55 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so1489849dad.13 for ; Fri, 26 Oct 2012 10:26:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=O4ZTMInsjKoIKARa1WmhzpPdMciDLosl3T9fw8Nday8=; b=U9L8uKhtDCNomjdw7eriS8VuEIogOFJ6lTNNkAq8U7l6/n2icbREeKirtD5qJtlk4y PPBBgmUDxAZIX6WRQtHkFoXa56hHOYLGIW5DJWcLimhGY/7RbAbfKgHYn3ODuBvDKJff 69NMGlHz64LPEp3DGagGsTU3IyJhKf+7x0ZtuVA2mfWhf/5bGsr8MXzh5gseCrOEdrCx FdMhdL4H27KXb2s2+1mMIbk9IrKwZ47pbtWpoO1zcdPg+JYwtb4c1GY80ElAbAECZ+U7 7gTRZTfJEq16HdzxRK5OsSbkDnS13g4svpvTcxecRtQWflrnB+FYF1ONjWQIyKexlGUd PfMA== MIME-Version: 1.0 Received: by 10.68.136.138 with SMTP id qa10mr72225018pbb.142.1351272384672; Fri, 26 Oct 2012 10:26:24 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.68.223.105 with HTTP; Fri, 26 Oct 2012 10:26:24 -0700 (PDT) Date: Fri, 26 Oct 2012 10:26:24 -0700 X-Google-Sender-Auth: QZnuq3VvIh6HmV9R6dTVRpkTQVI Message-ID: Subject: make tinderbox failures From: mdf@FreeBSD.org To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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 17:26:56 -0000 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. Thanks, matthew