In article <4481.1009549017@ocs3.intra.ocs.com.au> you write:
>Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>>Personally I've always considered make dep good enough. Its trying to solve
>>the extra .5% that probably can be solved by careful use of make clean when
>>CML realises a critical rule changed (SMP etc)
>
>http://prdownloads.sourceforge.net/kbuild/kbuild-2.5-history.tar.bz2
>Especially makefile-2.5_make_dep.html, 9 reasons why make dep is broken
>as designed. Some are fixable in the current system, others are
>inherently unfixable. I skipped that page when I did my presentation
>at the 2.5 developer's conference.
* make dep is only run once
Personally, I don't see this as a big problem. Just tell people to
always run "make oldconfig && make dep" after patching the kernel
and if they can't read, too bad. I usually compile a kernel a lot
more often than I add include files. Since I'm quite impatient
I often do "make SUBDIRS=drivers/mtd/maps modules" just so that the
compile will go faster, so having to do dependency checking each time
I want to compile feels like an unfortunate tradeoff to me.
* The generated dependencies are absolute
That dependencies are absolute is also not a thing that has bothered me
too much, it's always possible to run "make dep" after moving a tree,
on the other hand, I don't use NFS a lot anymore, so I can see it being
a problem in other environments.
/Christer
-- "Just how much can I get away with and still go to heaven?" - 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/
This archive was generated by hypermail 2b29 : Mon Dec 31 2001 - 21:00:17 EST