From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Satish Eerpini <eerpini@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: building custom module on 2.6.28 fails
Date: Sun, 25 Jan 2009 19:57:37 +0530 [thread overview]
Message-ID: <1232893657.10647.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20090125134712.GA29757@uranus.ravnborg.org>
On Sun, 2009-01-25 at 14:47 +0100, Sam Ravnborg wrote:
> On Sun, Jan 25, 2009 at 04:49:16PM +0530, Satish Eerpini wrote:
> > >> It seems you run "make clean" or "make distclean" in your kernel sources
> > >>
> > >> run "make prepare" in your kernel sources then you will not get this
> > >> error.
> > >
> >
> > I ran make clean and then make prepare but it gives an error saying
> > "no such file or directory : modpost ", ....
> > Then i ran make( in the kernel source tree) , and terminated it after
> > a few files were compiled and then again tried to compile my module,
> > this time it worked without any errors, ....... any particular reason
> > for this ??
> We are currently lacking a dependency on "scripts" so doing:
> make scripts
> make prepare
> is needed today.
As per makefile:
# make clean Delete most generated files
# Leave enough to build external modules
So is this OK to delete include/linux/bounds.h by 'make clean'.
--
JSR
next prev parent reply other threads:[~2009-01-25 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 4:57 Satish Eerpini
2009-01-25 6:49 ` Jaswinder Singh Rajput
2009-01-25 8:37 ` Satish Eerpini
2009-01-25 10:30 ` Jaswinder Singh Rajput
2009-01-25 10:40 ` Jaswinder Singh Rajput
2009-01-25 11:19 ` Satish Eerpini
2009-01-25 13:47 ` Sam Ravnborg
2009-01-25 14:27 ` Jaswinder Singh Rajput [this message]
2009-01-25 19:18 ` Sam Ravnborg
2009-01-25 19:32 ` Jaswinder Singh Rajput
2009-01-25 15:51 ` Satish Eerpini
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=1232893657.10647.4.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=eerpini@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®