Date: Wed, 8 Mar 2006 08:02:27 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Harti Brandt <harti@freebsd.org> Cc: deischen@freebsd.org, Dag-Erling Sm?rgrav <des@des.no>, current@freebsd.org Subject: Re: When will bsnmp stop breaking -current builds Message-ID: <20060308160227.GB5810@troutmask.apl.washington.edu> In-Reply-To: <20060308151239.D10582@beagle.kn.op.dlr.de> References: <Pine.GSO.4.43.0603071646040.8396-100000@sea.ntplx.net> <20060308085714.L10582@beagle.kn.op.dlr.de> <86bqwh59gn.fsf@xps.des.no> <20060308151239.D10582@beagle.kn.op.dlr.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 08, 2006 at 03:29:52PM +0100, Harti Brandt wrote: > On Wed, 8 Mar 2006, Dag-Erling Sm?rgrav wrote: > > DS>Harti Brandt <hartmut.brandt@dlr.de> writes: > DS>> You seem to be the only one having this problem, so this looks like > DS>> a problem on your side. > DS> > DS>Far from it. I had the same problem, and solved it by adding a > DS>NO_BSNMP knob (see attached patch). > > So you're the 2nd. Anyone else? I also wonder whether I overlooked a bug > report from you. I haven't seen this particular problem, but bsnmp has broken buildworld more than once due to what appears to be poorly tested patches. I simply disconnect the offending part of bsnmp from my builds. http://lists.freebsd.org/mailman/htdig/freebsd-current/2006-February/061183.html -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060308160227.GB5810>