path: root/Makefile
AgeCommit message (Collapse)Author
2005-07-12Linux 2.6.13-rc3v2.6.13-rc3Linus Torvalds
Yeah, this time hopefully I'm not confusing the version numbers. The last release was -rc2, _this_ is -rc3.
2005-07-07[PATCH] kbuild: build a single module using 'make dir/module.ko'Sam Ravnborg
Using the syntax: make dir/module.ko kbuild now allows one to build a module including the final link stage. This is usefull when one only wants to compile a single module and thus do not have to wait until a full kernel has finished compiling. Tested by: randy_dunlap <> Signed-off-by: Sam Ravnborg <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
2005-07-07[PATCH] kbuild: build TAGS problem with O=George Anzinger
make O=/dir TAGS fails with: MAKE TAGS find: security/selinux/include: No such file or directory find: include: No such file or directory find: include/asm-i386: No such file or directory find: include/asm-generic: No such file or directory The problem is in this line: ifeq ($(KBUILD_OUTPUT),) KBUILD_OUTPUT is not defined (ever) after make reruns itself. This line is used in the TAGS, tags, and cscope makes. Signed-off-by: George Anzinger <> Cc: Sam Ravnborg <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
2005-07-05Linux v2.6.13-rc3v2.6.13-rc2Linus Torvalds
2005-06-28Linux v2.6.13-rc1v2.6.13-rc1Linus Torvalds
Ok, a lot of things were pending after the 2.6.12 release, let's try to start calming things down again.
2005-06-25[PATCH] Makefile: s/gcc-option/cc-option/Alexey Dobriyan
Fixes Signed-off-by: Alexey Dobriyan <> Cc: Sam Ravnborg <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
2005-06-23[PATCH] Turn off sibling call optimization w/ frame pointersMatthias Urlichs
Frame pointers are supposed to enable debuggers to reliably tell where a call comes from. That is defeated by GCC's sibling call optimization (aka tail recursion elimination). This patch turns this optimization off when compiling with frame pointers. Signed-Off-By: Matthias Urlichs <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
2005-06-17Linux 2.6.12v2.6.12Linus Torvalds
2005-06-06Linux 2.6.12-rc6v2.6.12-rc6Linus Torvalds
Getting ready for the real release..
2005-05-24Linux 2.6.12-rc5v2.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 <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
2005-05-06Linux v2.6.12-rc4v2.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 <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
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 <> Signed-off-by: Linus Torvalds <>
2005-04-20Linux v2.6.12-rc3v2.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-rc2v2.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!