RELENG_5 broken?

[Kent Stewart]

On Thursday 14 April 2005 10:49 pm, Joel wrote:
> On Thu, 14 Apr 2005 22:32:42 -0700
> Kent Stewart <kstewart at owt.com> wrote
>
> > On Thursday 14 April 2005 09:23 pm, Joel wrote:
> > > On Thu, 14 Apr 2005 11:20:54 -0700
> > > Nate Lawson <nate at root.org> wrote
> > >
> > > > Jon Noack wrote:
> > > > > On 4/14/2005 8:28 AM, David Wolfskill wrote:
> > > > >> On Thu, Apr 14, 2005 at 01:26:17PM +0200, Jose M Rodriguez 
wrote:
> > > > >>> Anyone seen this?
> > > > >>
> > > > >> [...
> > > > >> /usr/src/sys/kern/subr_bus.c:1082: warning: no previous
> > > > >> prototype for 'devclass_get_drivers'
> > > > >> *** Error code 1
> > > > >> ...
> > > > >> ]
> > > > >>
> > > > >> Yup; just a few minutes ago, with sys/kern/subr_bus.c rev.
> > > > >> 1.156.2.6.
> > > > >>
> > > > >> Perhaps something was overlooked in the MFC from 2005-04-14
> > > > >> 04:54:15 UTC?
> > > > >
> > > > > Yeah, we also need to MFC rev. 1.68 of src/sys/sys/bus.h.
> > > >
> > > > I've committed the prototype, much apologies for the breakage. 
> > > > I compiled the patch in my RELENG_5 tree just fine, but it
> > > > appears the kernel build may be referencing /sys for includes
> > > > instead of ../../../sys or whatever.  Thus build-testing MFC
> > > > patches on a -current box is not a good test.
> > >
> > > Okay, I started a build makeworld in /usr/src last night, and
> > > then build make kernel hits this.
> > >
> > > What do we do next? Is it okay to go back to cvsup, and will that
> > > pick up the changes?
> >
> > Joel,
> >
> > Can I give you a bad time.
>
> Of course. My kids would say I deserve it, too, since I'm such a
> tease around the house.
>
> > We were always told that if you follow
> > x-stable, you were to follow cvs-all.
>
> ... as in editing the example to set the default host to
> cvsup3.jp.freebsd.org, and doing
>
>     sudo cvsup -g -L 2 stable-supfile
>
> right before the make buildworld?
>
> > Then, you would have seen his fix
> > committed around 1811 UTC.
>
> I think I was in bed by then. (UTC+9 here.)
>
> > FWIW, you are just in time anyway because they added a security
> > notice and if you cvsup now, you will also get that fix.
>
> So the system is not in an unstable situation such that repeating the
> cvsup would have me trying to build from inconsistent libraries or
> anything like that?

When you do the buildworld, you get a new world and then the kernel will 
build. This is one of the reasons to buildworld, buildkernel, and 
install kernel. Since the buildkernel died, your libraries haven't been 
updated. You wouldn't do that until after you have booted the new 
kernel in single user mode. The sequence may be awkward at times but it 
saves you from the little disasters :).

>
> What the heck, I'll take a backup and give it a spin.

Just remember you build and install the world and the kernel. I just got 
through upgrading to get the ifconf fix. No, problem.

Kent

>
> Thanks.
>
> --
> Joel Rees   <rees at ddcom.co.jp>
> digitcom, inc.   株式会社デジコム
> Kobe, Japan   +81-78-672-8800
> ** <http://www.ddcom.co.jp> **
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
> "freebsd-stable-unsubscribe at freebsd.org"

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html