From: Sam Ravnborg <sam@ravnborg.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, agruen@suse.de
Subject: Re: Building external modules against objdirs
Date: Sun, 30 Jul 2006 20:31:59 +0200 [thread overview]
Message-ID: <20060730183159.GA30278@mars.ravnborg.org> (raw)
In-Reply-To: <200607301949.41165.ak@suse.de>
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
next prev parent reply other threads:[~2006-07-30 18:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 16:46 Building external modules against objdirs Andi Kleen
2006-07-30 17:51 ` Sam Ravnborg
2006-07-30 17:49 ` Andi Kleen
2006-07-30 18:31 ` Sam Ravnborg [this message]
2006-07-30 18:37 ` Andi Kleen
2006-07-30 19:17 ` Sam Ravnborg
2006-07-30 20:06 ` Andi Kleen
2006-07-31 9:39 ` Roman Zippel
2006-08-01 19:42 ` Sam Ravnborg
2006-07-30 18:34 ` Sam Ravnborg
2006-07-30 18:42 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060730183159.GA30278@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=agruen@suse.de \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox