From owner-freebsd-current@FreeBSD.ORG Thu Mar 23 08:06:33 2006 Return-Path: X-Original-To: freebsd-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 6CECB16A400 for ; Thu, 23 Mar 2006 08:06:33 +0000 (UTC) (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 CB86F43D48 for ; Thu, 23 Mar 2006 08:06:32 +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); Thu, 23 Mar 2006 09:06:30 +0100 Date: Thu, 23 Mar 2006 09:06:33 +0100 (CET) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: othermark In-Reply-To: Message-ID: <20060323090509.L1366@beagle.kn.op.dlr.de> References: <4421CE88.1010104@FreeBSD.org> <20060322224936.3F76C45041@ptavv.es.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 23 Mar 2006 08:06:30.0449 (UTC) FILETIME=[B13C0A10:01C64E50] Cc: freebsd-current@freebsd.org Subject: Re: buildworld Stop in /usr/src/usr.sbin/bsnmpd/bsnmpd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Mar 2006 08:06:33 -0000 On Wed, 22 Mar 2006, othermark wrote: o>Kevin Oberman wrote: o>> > Date: Wed, 22 Mar 2006 14:24:08 -0800 o>> > From: Jason Evans o>> > o>> > Kevin Oberman wrote: o>> > o>> > > > From: othermark o>> > > > Date: Wed, 22 Mar 2006 12:13:14 -0800 o>> > > > Sender: owner-freebsd-current@freebsd.org o>> > > > o>> > > > I'm scratching my head on this one, trying to buildworld with today o>> > > > sources o>> > > > to get the sendmail fix: o>> > > o>> > > o>> > > I am seeing the same thing. I read the tread on this from back on March o>> > > 7-9 and have confirmed that the "fix" is in my Makefile.inc1, but I o>> > > still can't make buildworld. o>> > > o>> > > My last update was in the critical perion...Feb. 23, but I have been o>> > > unsuccessful in getting past it. o>> > > o>> > > I have tried explicitly running the newly built getsnmptree (from o>> > > /usr/obj) and then building, but I have had no luck to this point. o>> > > o>> > > Not only did the fix to Makefile.inc1 not do the trick, but o>> > > hand-building gnesnmptree and hand executing the commands to make the o>> > > oid.h file didn't help a bit. o>> > > o>> > > I'm baffled. (And probably missing the obvious.) o>> > o>> > This isn't a very satisfying solution, but if you do the buildworld with o>> > MALLOC_OPTIONS=jZ, you will avoid the gensnmptree bug. o>> > o>> > Jason o>> > o>> o>> o>> Jason, o>> o>> Thanks! It worked like a charm. o>> o>> Any explanation as to why zeroing a malloc makes this work (as opposed o>> to filling with 0xa5)? I'm sure confused. o> o>Double thanks, I was finally able to get a successful buildworld. What is o>the likelyhood of other people hitting this? This boxes' -current was only o>27 days old, before I tried this update. It should not, because gensnmptree is now a buildtool. To find out what goes wrong we need the buildworld log that Ruslan mentioned. harti