Is it safe to interrupt (Ctrl + C) while building a port or kernel?

[Erik Trulsson]

On Thu, Nov 03, 2011 at 01:48:47PM -0500, Robert Bonomi wrote:
> 
> On Thu, 03 Nov 2011 18:29:06 +0100, Damien Fleuriot <ml at my.gd) wrote:
> > On 11/3/11 6:20 PM, Robert Bonomi wrote:
> > >> From owner-freebsd-questions at freebsd.org  Thu Nov  3 12:10:08 2011
> > >> From: =?koi8-r?B?4c7Uz84g68zF09M=?= <rc5hack at yandex.ru>
> > >> To: freebsd-questions at freebsd.org
> > >> Date: Thu, 03 Nov 2011 21:10:19 +0400
> > >> Subject: Is it safe to interrupt (Ctrl + C) while building a port or kernel?
> > >>
> > >> Sometimes, while building process of some port or system kernel are in progress, you suddenly remember that you did something wrong and have to stop, solve your mistake and start one more time.
> > >>
> > >> Is it clear to interrupt the building process just by pressing Ctrl + <C>?
> > > 
> > > Yes.
> > > 
> > >> If it's so, do I need to run "make clean" before I start "make" one more time?
> > > 
> > > Authoritative answer:  "It depends".
> > > 
> > > On what you 'did wrong", and what it takes to fix it.
> > > 
> > > e.g.,  if you're building a kernel the 'classial' way, that is 'configure,
> > > make depend, cd , make',  and realize you left something out of the config
> > > file, after you edit the config file, you have to rerun _all_ those steps.
> > > 
> >
> > Is it even advisable to build the kernel the "old" way ?
> 
> On a slow processor, it makes a *BIG* differnence.
> Even more so if you build everything you need into the kernel.
> 
> 'make buildkernel' always recompiles an relinks *everything*. whether or
> not any dependenies for the module have changed.

If that is a problem then just use 'make -DNO_CLEAN buildkernel' and
it won't reompile stuff that doesn't need to be recompiled.  (Works for
buildworld as well.)


-- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013 at student.uu.se