aboutsummaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorKai Germaschewski <kai@tp1.ruhr-uni-bochum.de>2003-03-02 10:55:36 -0600
committerKai Germaschewski <kai@tp1.ruhr-uni-bochum.de>2003-03-02 10:55:36 -0600
commitdb0d626379ebc2d19f05f382fdf4b04b287763e6 (patch)
tree9a75aaf769839a99cf0f46a4452e69c81dde9599 /Makefile
parent41f57979ec9ab9e87e0c58fd845c01acdb7021cc (diff)
downloadhistory-db0d626379ebc2d19f05f382fdf4b04b287763e6.tar.gz
kbuild: remove dependency on compile.h
We had a dummy dependency on include/linux/compile.h, but it really caused more trouble than benefits. It's not actually needed for the module postprocessing, it was only put there to make sure we recognize when gcc changed under us. However, we really can only do so much, and the rest of kbuild won't notice a changed gcc either, so if the user replaces gcc during a build, he just can't rely on the build doing the right thing. The common cases are still covered, anyway. When the command to invoke gcc changes ("CC=gcc32") we notice, and when the path to /usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdarg.h changes (which luckily contains the "2.96", we'll notice and handle that, too.
Diffstat (limited to 'Makefile')
-rw-r--r--Makefile5
1 files changed, 1 insertions, 4 deletions
diff --git a/Makefile b/Makefile
index c95de1620be27..2b32613879039 100644
--- a/Makefile
+++ b/Makefile
@@ -501,11 +501,8 @@ all: modules
# Build modules
-include/linux/compile.h: FORCE
- $(Q)$(MAKE) $(build)=init include/linux/compile.h
-
.PHONY: modules
-modules: $(SUBDIRS) $(if $(KBUILD_BUILTIN),vmlinux) include/linux/compile.h
+modules: $(SUBDIRS) $(if $(KBUILD_BUILTIN),vmlinux)
@echo ' Building modules, stage 2.';
$(Q)$(MAKE) -rR -f scripts/Makefile.modpost