aboutsummaryrefslogtreecommitdiff
path: root/Makefile
AgeCommit message (Collapse)Author
2005-05-24Linux 2.6.12-rc5Linus Torvalds
2005-05-17[PATCH] Makefile include path orderingRik van Riel
The arch Makefile may override the include path order, which is used by Xen (and UML?) to make sure include/asm-xen is searched before include/asm-i386. The Makefile change to 2.6.12-rc4 made the top Makefile always override the value specified by the arch Makefile. This trivial patch makes the Xen kernel compile again. Signed-off-by: Rik van Riel <riel@redhat.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-05-06Linux v2.6.12-rc4Linus Torvalds
2005-05-01[PATCH] Makefile: fix for compatibility with *emacs ctagsEmanuele Giaquinta
I've noticed that, starting from linux-2.6.12-rc1, in the top Makefile the "cmd_tags" variable has been changed in a way incompatible with *emacs ctags. Since the "--extra" option exists only in "exuberant ctags", it should be included in the CTAGSF shell variable. Cc: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-04-30[PATCH] kbuild: Set NOSTDINC_FLAGS late to speed up compile (a little)Sam Ravnborg
Move definition of NOSTDINC_FLAGS below inclusion of arch Makefile, so any arch specific settings to $(CC) takes effect before looking up the compiler include directory. The previous solution that replaced ':=' with '=' caused gcc to be invoked one additional time for each directory visited. This decreases kernel compile time with 0.1 second (3.6 -> 3.5 seconds) when running make on a fully built kernel Signed-off-by: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-04-20Linux v2.6.12-rc3Linus Torvalds
Releasing this will also make "git" the official source control thing. Here's to hoping for the best.
2005-04-16Linux-2.6.12-rc2Linus Torvalds
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!