Re: buildworld Stop in /usr/src/usr.sbin/bsnmpd/bsnmpd

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 <jasone_at_FreeBSD.org>
o>> > 
o>> > Kevin Oberman wrote:
o>> > 
o>> > > > From: othermark <atkin901_at_yahoo.com>
o>> > > > Date: Wed, 22 Mar 2006 12:13:14 -0800
o>> > > > Sender: owner-freebsd-current_at_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