lkml.org 
[lkml]   [2001]   [Oct]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [patch] 2.4.11-pre4 remove spurious kernel recompiles
Date
On Sun, 7 Oct 2001 13:16:19 -0500 (CDT), 
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>On Sun, 7 Oct 2001, Andrea Arcangeli wrote:
>
>> On Sun, Oct 07, 2001 at 08:25:42PM +1000, Keith Owens wrote:
>> > in the top level Makefile forces a recompile of the entire kernel, for
>> > no good reason.
>>
>> this is a matter of taste but personally I believe that at least
>> theorically recompiling the whole kernel if I add -g to CFLAGS, or if I
>> change the EXTRAVERSION have lots of sense.
>
>Correct. I am amazed Keith missed this... changing data in Makefile
>can certainly affect the entire kernel compile, so it makes sense to
>recompile the entire kernel when it changes.

I did not miss it. Changing cflags is detected by the
.<object>.o.flags files.

ifeq (-D__KERNEL__ -I/build/kaos/2.4.11-pre4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586,$(strip $(subst $(comma),:,$(CFLAGS) $(EXTRA_CFLAGS) $(CFLAGS_vt.o))))
FILES_FLAGS_UP_TO_DATE += vt.o
endif

kbuild already detects changes to flags, down to the level of
per-object flags, there is no need to detect changes to the top level
Makefile. Especially when you can override flags and other fields on
the make command line, that does not change Makefile but kbuild still
detects the changes.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:04    [W:0.089 / U:5.568 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site