From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kbuild- sub directroy makefile
Date: Wed, 22 Apr 2015 19:12:15 +0200 [thread overview]
Message-ID: <20150422171215.GC2551@kroah.com> (raw)
In-Reply-To: <CAGZFCEF5pzsvHi24NPCktfThtKE4141pz7m31f8=8kRC1Mz=Xw@mail.gmail.com>
On Wed, Apr 22, 2015 at 09:42:59PM +0530, ratheesh kannoth wrote:
> On Wed, Apr 22, 2015 at 9:36 PM, Greg KH <greg@kroah.com> wrote:
> > Nope, why do you want to do that? The kernel build will show you that
> > hello.o is being built, when it is built.
>
> Greg,
> There was some problem with env variables ( that i exported to shell
> from top ) that my makefile is using.
Kernel makefiles should not be using any environment variables. Your
makefile should be almost exactly what you posted, just a list of the .o
files it takes to build the module. Nothing else is needed.
If it is, you are making things much harder than they should be :)
thanks,
greg k-h
prev parent reply other threads:[~2015-04-22 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 15:41 kbuild- sub directroy makefile ratheesh kannoth
2015-04-22 16:06 ` Greg KH
2015-04-22 16:12 ` ratheesh kannoth
2015-04-22 17:12 ` Greg KH [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=20150422171215.GC2551@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).