On Sun, Jul 30, 2006 at 07:49:41PM +0200, Andi Kleen wrote:
>
> > Can you check that you really did a 'make prepare' in the relevant
> > output directory. Previously only the make *config step was needed.
>
> The output directory is a full build (configuration + make without any targets).
> Is that not enough anymore?
>
> Anyways after a make prepare it seems to work - thanks - but I think that
> should be really done as part of the standard build like it was in 2.6.17.
'make prepare' is and has always been part of the standard build.
So I really do not see what is going on.
Can you please check that followign files exists in your output
directory:
.config
include/config/auto.conf.cmd
include/config/auto.conf
the latter should be the latest of the three.
Also try applying following patch to reveal why we trigger this rule:
diff --git a/Makefile b/Makefile
index 1dd58d3..4c30ed5 100644
--- a/Makefile
+++ b/Makefile
@@ -453,6 +453,7 @@ include/config/auto.conf: $(KCONFIG_CONF
ifeq ($(KBUILD_EXTMOD),)
$(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig
else
+ @echo triggered by - $? -
$(error kernel configuration not valid - run 'make prepare' in $(srctree) to update it)
endif
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
