From owner-freebsd-current@FreeBSD.ORG  Wed Mar  8 18:58:17 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 4050116A420;
	Wed,  8 Mar 2006 18:58:17 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BFE9B43D55;
	Wed,  8 Mar 2006 18:58:16 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1] (may be forged))
	by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k28ItdPZ026952;
	Wed, 8 Mar 2006 11:55:40 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Wed, 08 Mar 2006 11:55:39 -0700 (MST)
Message-Id: <20060308.115539.98861830.imp@bsdimp.com>
To: keramida@ceid.upatras.gr
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20060308152413.GA43764@flame.pc>
References: <20060308085714.L10582@beagle.kn.op.dlr.de>
	<86bqwh59gn.fsf@xps.des.no> <20060308152413.GA43764@flame.pc>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0
	(harmony.bsdimp.com [127.0.0.1]);
	Wed, 08 Mar 2006 11:55:41 -0700 (MST)
Cc: deischen@FreeBSD.ORG, des@des.no, harti@FreeBSD.ORG, current@FreeBSD.ORG,
	ru@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
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 18:58:17 -0000

In message: <20060308152413.GA43764@flame.pc>
            Giorgos Keramidas <keramida@ceid.upatras.gr> writes:
: On 2006-03-08 14:53, Dag-Erling Sm?rgrav <des@des.no> wrote:
: > Harti Brandt <hartmut.brandt@dlr.de> writes:
: > > You seem to be the only one having this problem, so this looks like
: > > a problem on your side.
: >
: > Far from it.  I had the same problem, and solved it by adding a
: > NO_BSNMP knob (see attached patch).
: >
: > The deeper problem is that gensnmptree is a build tool, but isn't
: > treated as such by the build system, so cross-builds and source
: > updates from older versions are broken.
: 
: I solved the original gensnmptree problems I had when I moved back and
: forth around January 25-26th builds, with:
: 
: %%%
: Index: Makefile.inc1
: ===================================================================
: --- Makefile.inc1       (revision 19)
: +++ Makefile.inc1       (working copy)
: @@ -839,6 +839,7 @@
:      usr.bin/rpcgen \
:      usr.bin/xinstall \
:      usr.sbin/config \
: +    usr.sbin/bsnmpd/gensnmptree \
:      ${_crunchgen} \
:      ${_pwd_mkdb}
:         ${_+_}@${ECHODIR} "===> ${_tool} (obj,depend,all,install)"; \
: %%%
: 
: Things worked fine after this :)

This seems like a reasonable thing to do for now, since it is clear
that regardless of theory, gensnmptree in practice is a buildtool.

Warner