From owner-freebsd-current@FreeBSD.ORG  Wed Mar  8 14:28:30 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 B7C5516A420;
	Wed,  8 Mar 2006 14:28:30 +0000 (GMT)
	(envelope-from Hartmut.Brandt@dlr.de)
Received: from smtp-3.dlr.de (smtp-3.dlr.de [195.37.61.187])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E2C7D43D45;
	Wed,  8 Mar 2006 14:28:29 +0000 (GMT)
	(envelope-from Hartmut.Brandt@dlr.de)
Received: from beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-3.dlr.de over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 8 Mar 2006 15:28:27 +0100
Date: Wed, 8 Mar 2006 15:28:28 +0100 (CET)
From: Harti Brandt <hartmut.brandt@dlr.de>
X-X-Sender: brandt_h@beagle.kn.op.dlr.de
To: Daniel Eischen <deischen@freebsd.org>
In-Reply-To: <Pine.GSO.4.43.0603080815470.13113-100000@sea.ntplx.net>
Message-ID: <20060308152441.V10582@beagle.kn.op.dlr.de>
References: <Pine.GSO.4.43.0603080815470.13113-100000@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 08 Mar 2006 14:28:27.0655 (UTC)
	FILETIME=[90C1E970:01C642BC]
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: Harti Brandt <harti@freebsd.org>
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Mar 2006 14:28:30 -0000

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 $

DE>If I build (buildworld, without installworld) -current on a
DE>6-stable box, the build works and the generated tree.c does
DE>not have the unreferenced fuunctions.  Manually running
DE>gensnmptree from obj/.../bsnmpd/gensnmptree/gensnmptree
DE>on tree.def also does not produce a tree.c with the unreferenced
DE>functions.
DE>
DE>> Could you send me the tree.c from the object
DE>> directory (usr.sbin/bsnmpd/bsnmpd/tree.c)? Do you cross build?
DE>
DE>No, I don't cross build.  CFLAGS=-O -pipe
DE>I'll send that to you when I get back to work.

Ok.

harti