Date: Wed, 8 Mar 2006 17:26:24 +0100 (CET) From: Harti Brandt <hartmut.brandt@dlr.de> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: current@freebsd.org Subject: Re: When will bsnmp stop breaking -current builds Message-ID: <20060308172009.I10582@beagle.kn.op.dlr.de> In-Reply-To: <20060308160227.GB5810@troutmask.apl.washington.edu> 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> <20060308160227.GB5810@troutmask.apl.washington.edu>
index | next in thread | previous in thread | raw e-mail
On Wed, 8 Mar 2006, Steve Kargl wrote: SK>On Wed, Mar 08, 2006 at 03:29:52PM +0100, Harti Brandt wrote: SK>> On Wed, 8 Mar 2006, Dag-Erling Sm?rgrav wrote: SK>> SK>> DS>Harti Brandt <hartmut.brandt@dlr.de> writes: SK>> DS>> You seem to be the only one having this problem, so this looks like SK>> DS>> a problem on your side. SK>> DS> SK>> DS>Far from it. I had the same problem, and solved it by adding a SK>> DS>NO_BSNMP knob (see attached patch). SK>> SK>> So you're the 2nd. Anyone else? I also wonder whether I overlooked a bug SK>> report from you. SK> SK>I haven't seen this particular problem, but bsnmp has broken SK>buildworld more than once due to what appears to be poorly SK>tested patches. I simply disconnect the offending part SK>of bsnmp from my builds. SK> SK>http://lists.freebsd.org/mailman/htdig/freebsd-current/2006-February/061183.html The patch was ok, just forgetting to commit one of the files was not. This was fixed very fast by ru. I usually test all patches with making a universe and building on both i386 and sparc64 and running them on both machines. There is hardly more one could do. hartihome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060308172009.I10582>