On Tue, Jun 16, 2009 at 11:39 AM, Hauke Mehrtens<hauke@xxxxxxxxxx> wrote: > Jan Kiszka wrote: >> Including config.mk again when kbuild called into the top level Makefile >> slowed down the build process awfully. The reason for this were all the >> dynamic, shell-based variable evaluations that were called over and over >> again. Fortunately, including config.mk only in the outer Makefile run >> appears to be enough. So let's remove this warp speed blocker. >> >> Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxx> >> --- >> Makefile | 2 -- >> 1 files changed, 0 insertions(+), 2 deletions(-) >> >> diff --git a/Makefile b/Makefile >> index 0ab7d27..49a786a 100644 >> --- a/Makefile >> +++ b/Makefile >> @@ -13,8 +13,6 @@ OLD_IWL=$(shell $(MODPROBE) -l iwl4965) >> >> ifneq ($(KERNELRELEASE),) >> >> -include $(M)/$(COMPAT_CONFIG) >> - >> NOSTDINC_FLAGS := -I$(M)/include/ -include $(M)/include/net/compat.h $(CFLAGS) >> >> obj-y := net/wireless/ net/mac80211/ net/rfkill/ > > Hi Jan, > > I have tested this patch and it reduced the build time for me from 3:30 > to 2:40 minutes on a dual core system. I can not see any changes, expect > the reduced build time on my system. The resulting modules are still the > same. Reason for including the config.mk is if your current kernel config differs the makefiles won't pick up the new stuff. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
