Very Computer

by **frpl..** » Fri, 26 Jan 2001 01:39:04

What is the benefit of running "make clean" in between "make dep"
and "make bzImage"?

I ask cause I've seen this on a redhat tutorial, but is not stated in
the kernel readme.

Sent via Deja.com
http://www.deja.com/

by **sch..** » Fri, 26 Jan 2001 01:57:38

> What is the benefit of running "make clean" in between "make dep"
> and "make bzImage"?

> I ask cause I've seen this on a redhat tutorial, but is not stated in
> the kernel readme.

> Sent via Deja.com
> http://www.deja.com/

When the configure script ends, it tells you to `make dep' and
(possibly) `clean'. This insures that all of the dependencies, such the
include files, are in place. When finished, you should do a `make
clean'. This removes all of the object files and some other things that
an old version leaves behind. In any case, do not forget this step
before attempting to recompile a kernel.

Scott
-----
Support provided by Linuxgruven, Inc.
www.linuxgruven.com
314-727-0918

Sent via Deja.com
http://www.deja.com/

by **pbloomg..** » Fri, 26 Jan 2001 02:03:35

> What is the benefit of running "make clean" in between "make dep"
> and "make bzImage"?

> I ask cause I've seen this on a redhat tutorial, but is not stated in
> the kernel readme.

> Sent via Deja.com
> http://www.deja.com/

The make clean purges any now-unwanted files left from previous builds
of the kernel.

Paul
-------
Support provided by Linuxgruven, Inc.
www.linuxgruven.com
314-727-0918

Sent via Deja.com
http://www.deja.com/

by **Norman Levi** » Sat, 27 Jan 2001 07:17:33

> What is the benefit of running "make clean"

** gets rid of ???.o files so you are 'starting clean' when kernel is built.

in between "make dep"

Quote:> and "make bzImage"?

> I ask cause I've seen this on a redhat tutorial, but is not stated in
> the kernel readme.

> Sent via Deja.com
> http://www.deja.com/

--
Norman Levin

greatest power, the village idiot will come forth to be acclaimed the
leader.'"

by **Norman Levi** » Sat, 27 Jan 2001 07:20:06

> >What is the benefit of running "make clean" in between "make dep"
> >and "make bzImage"?

> >I ask cause I've seen this on a redhat tutorial, but is not stated in
> >the kernel readme.

> It cleans up the files from previous make round. Normally you don't want
> to do that, as leaving them will speed the compilation process up. Make
> is designed to only recompile those sections of source code that have
> changed since the previous time make was used, or the sections which are
> effected by a change in configuration. Normally make will insure that
> when you fi add a module to support a new network interface card, you
> won't waste CPU cycles by recompiling your audio modules. In principle.

** Is this really true? It seems that one of the makes goes around and 'touches'
every blasted piece of source so it looks like somebody updated every routine and I go
thru an ENTIRE COMPILE of the kernel even if I change only one thing! Maybe it
is the "make clean" that is doing that?

> Now sometimes the dependancies in the makefile aren't 100% tight so that
> after a change make would not recompile every piece of source code
> effected by that change. That is were the make clean comes in. That
> cleans up all previously compiled sections, and makes sure everything is
> compiled and no stale .o files are included.

> So make clean may be usefull, but may also force you to longer compile
> times.
> --
> If a trainstation is the place where trains stop, what is a workstation?
> ------------------------------------------------------------------------

> The Netherlands website: http://hermanbruijn.com

--
Norman Levin

greatest power, the village idiot will come forth to be acclaimed the
leader.'"

Very Computer

general kernel compile question

general kernel compile question

general kernel compile question

general kernel compile question

general kernel compile question

general kernel compile question