Ok, fair enough.  I have to confess that my usual procedure remains,
as it has been for a long time, like this:

1) rm -r /usr/include; cd /usr/src; make includes

This may be controversial, but it has always worked for me, and although
it's not supposed to (in my understanding), the build (I think both world
and kernel) does use installed headers.  If you don't think so, mv
/usr/include and then try to build either.

2) cd usr.sbin/config; make obj && make depend && make && make install

3) config and build kernel

4) make buildworld

5) install kernel

6) make installworld

7) update /etc if necessary

8) reboot

Here lately, I have been trying to break this cycle and use the

1) make buildworld

2) make buildkernel

3) make installkernel

4) make installworld

5) reboot

cycle instead, since I have been assured that this is the canonical
way of doing things now.  It appears that these pronouncements were
premature at best.

On Sun, Jan 21, 2001 at 11:12:44PM -0800, John Baldwin wrote:
> Rarely if ever do you need the new tools.  The only cases are for a binutils
> upgrade that is not backwards compatible (such as the 2.9 -> 2.10 upgrade), or
> if you need a newer version of config, which can be handled by installing
> config and then building your kernel.  The config(8) changes won't happen in
> stable, and I don't foresee anymore drastic buildkernel changes in the future.
> FWIW, I _never_ use buildkernel to update my kernels on any of my boxes.  I
> just do it the old fashioned way, and with the exception of the 2.9 -> 2.10
> binutils upgrade, it always works.  buildkernel overloads the KERNEL variable
> and thus violates POLA, so it needs fixing regardless, but I don't see a reason
> to encourage its use unless it is actually needed.
> -- 
> John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
> "Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to