From: "Tej Parkash" <tejparkash.d@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reg: modules make in Ubuntu
Date: Sat, 26 May 2007 04:08:39 -0400 [thread overview]
Message-ID: <2bd9ebfa0705260108t67f33613p1e31683741c7507@mail.gmail.com> (raw)
In-Reply-To: <20070526065835.GA22020@uranus.ravnborg.org>
On 5/26/07, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Sat, May 26, 2007 at 01:28:56AM -0400, Tej Parkash wrote:
> > make[1]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic'
> > CHK include/linux/version.h
> > CHK include/linux/utsrelease.h
> > make[2]: *** No rule to make target `arch/i386/kernel/msr.c', needed
> > by `arch/i386/kernel/msr.o'. Stop.
> > make[1]: *** [arch/i386/kernel] Error 2
> > make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic'
> > make: *** [all] Error 2
> >
> > what the hack is this. no kernel version is having this file in this
> > particular location as asked in error. then why this error is coming
> > in this kernel version.
> Looks like you are trying to build a kernel but have only headers
> judging from the directoryname.
yaa u r correct
but i am wondering like how those file can be missed from the required
location. if they are so important to build the module.. even if it is
missed is there any other procedure to build the module
i am trying it on other kernel version.
>
> Could you please prove a bit more context if you need additional help.
> Like (but not limited to):
> -> Actual commandline
> -> Any own kbuild/Makefiles
> -> .config
>
> Sam
>
thanks
tej
prev parent reply other threads:[~2007-05-26 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 5:28 Tej Parkash
2007-05-26 6:58 ` Sam Ravnborg
2007-05-26 8:08 ` Tej Parkash [this message]
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=2bd9ebfa0705260108t67f33613p1e31683741c7507@mail.gmail.com \
--to=tejparkash.d@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®