From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Rich Chase <rac47.02@engalumni.colostate.edu>,
linux-kernel@vger.kernel.org
Subject: Re: missing elfconfig.h
Date: Sat, 9 Jun 2007 10:53:09 +0200 [thread overview]
Message-ID: <20070609085309.GB30611@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0706090952250.4353@fbirervta.pbzchgretzou.qr>
On Sat, Jun 09, 2007 at 09:53:22AM +0200, Jan Engelhardt wrote:
>
> On Jun 8 2007 22:19, Sam Ravnborg wrote:
> >On Fri, Jun 08, 2007 at 09:08:36AM -0400, Rich Chase wrote:
> >> An Apparent bug:
> >> version 2.6.21.3
> >> missing the file ./scripts/mod/elfconfig.h
> >
> >To build an external module you need to point to a directory
> >where a fully build kernel is placed.
> >
> >You could do a full build and then a "make clean",
> >this would still let you build external modules.
>
> Is not "make prepare" enough?
>
> >In your case the kernel was not build.
> >And to build modpost you need to execute "make modules" from
> >the kernel top-level directory.
>
> "make scripts" ?
It depnes on the module. If the module uses MODVERSIONIGN a full
build is needed.
For the naive case make *config; make prepare; make scripts are enough.
But I encourage a full make and then make clean because that works in
all situations.
Sam
next prev parent reply other threads:[~2007-06-09 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 13:08 Rich Chase
2007-06-08 20:19 ` Sam Ravnborg
2007-06-09 7:53 ` Jan Engelhardt
2007-06-09 7:57 ` Robert P. J. Day
2007-06-09 8:54 ` Sam Ravnborg
2007-06-09 7:59 ` Robert P. J. Day
2007-06-09 8:53 ` Sam Ravnborg [this message]
2007-06-09 16:38 ` Rich Chase
2007-06-09 16:24 ` Rich Chase
2007-06-09 20:57 ` Sam Ravnborg
2007-06-09 16:34 Rich Chase
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=20070609085309.GB30611@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rac47.02@engalumni.colostate.edu \
/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
all inboxes | Powered by JetHome®