From owner-freebsd-current@FreeBSD.ORG Wed Mar 8 14:34:47 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DED7E16A420; Wed, 8 Mar 2006 14:34:47 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6915D43D48; Wed, 8 Mar 2006 14:34:47 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id k28EYkNX028863; Wed, 8 Mar 2006 09:34:46 -0500 (EST) Date: Wed, 8 Mar 2006 09:34:46 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Harti Brandt In-Reply-To: <20060308152441.V10582@beagle.kn.op.dlr.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: current@freebsd.org Subject: Re: When will bsnmp stop breaking -current builds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Mar 2006 14:34:48 -0000 On Wed, 8 Mar 2006, Harti Brandt wrote: > On Wed, 8 Mar 2006, Daniel Eischen wrote: > > DE>On Wed, 8 Mar 2006, Harti Brandt wrote: > DE> > DE>> On Tue, 7 Mar 2006, Daniel Eischen wrote: > DE>> > DE>> DE>We have this problem on 3 different systems. What's going on. > DE>> DE>Can I please remove bsnmpd from the build???? > DE>> > DE>> You seem to be the only one having this problem, so this looks like a > DE>> problem on your side. Generally the gensnmptree tool does not put a > DE>> reference to these functions into tree.c because the MIB variables they > DE>> are attached to are all no-access. So either you use a wrong gensnmptree > DE>> (a very old one), or there is something wrong with > DE>> contrib/bsnmp/snmpd/tree.def. > DE> > DE>The systems having the problem are running from worlds built > DE>within the last couple of weeks. I've tried manually building > DE>tree.c from both the installed gensnmptree and the new buildworld > DE>gensnmptree (using the gensnmptree from /usr/obj/... after the > DE>world failed). Both generate the unreferenced functions in > DE>tree.c. > > That's very strange. Could you please lookup the Revisions of > contrib/bsnmp/gensnmptree/gensnmptree.c and contrib/bsnmp/snmpd/tree.def? > The actual revisions are: > > $Begemot: bsnmp/gensnmptree/gensnmptree.c,v 1.44 2006/02/14 09:04:17 brandt_h Exp $ > $Begemot: bsnmp/snmpd/tree.def,v 1.38 2004/08/06 08:47:17 brandt Exp $ Yes, everything is up to date. We've cleaned out the entire src and obj trees, rechecked out -current, tried CVSup'ing from different CVSup servers, and manually checked the file versions against the main CVS repo (using www.freebsd.org cvsweb). -- DE