e finished bask in the glow of a job well done ...
> > >
> > > Thanks
> > >
> > >
> > > ----- Original Message -
> > > From: Jordan K. Hubbard <[EMAIL PROTECTED]>
> > > To: Warner Losh <[EMAIL PROTECTED]>
> > &
e
> > 2.2.8-stable -> 3.2-stable
> >
> > When you're finished bask in the glow of a job well done ...
> > >
> > > Thanks
> > >
> > >
> > > ----- Original Message -
> > > From: Jordan K. Hubbard <[EMAIL
t; >
> > - Original Message -
> > From: Jordan K. Hubbard <[EMAIL PROTECTED]>
> > To: Warner Losh <[EMAIL PROTECTED]>
> > Cc: Mike Smith <[EMAIL PROTECTED]>; John <[EMAIL PROTECTED]>;
> > <[EMAIL PROTECTED]>
> > Sent: Thur
osh <[EMAIL PROTECTED]>
> Cc: Mike Smith <[EMAIL PROTECTED]>; John <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Thursday, June 24, 1999 1:05 AM
> Subject: Re: 2.2.8->3.2 woes
>
>
> > Absolutely. Whether you're going from 2.2.x to 3.
EMAIL PROTECTED]>; John <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, June 24, 1999 1:05 AM
Subject: Re: 2.2.8->3.2 woes
> Absolutely. Whether you're going from 2.2.x to 3.x or 2.2.x to 4.0,
> it's the same set of problems. :)
>
> >
> Well, I've tried several things over the past couple of weeks, with the
> following results:
>
> make world - the error i mentioned already
> make buildworld - same error
These will have already left you somewhat screwed. It's not possible
now to expect an automated upgrade to just work since
