Date: Wed, 8 Mar 2006 17:24:13 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Dag-Erling Sm?rgrav <des@des.no> Cc: deischen@freebsd.org, Harti Brandt <harti@freebsd.org>, current@freebsd.org Subject: Re: When will bsnmp stop breaking -current builds Message-ID: <20060308152413.GA43764@flame.pc> In-Reply-To: <86bqwh59gn.fsf@xps.des.no> References: <Pine.GSO.4.43.0603071646040.8396-100000@sea.ntplx.net> <20060308085714.L10582@beagle.kn.op.dlr.de> <86bqwh59gn.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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 :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060308152413.GA43764>