All of lore.kernel.org
 help / color / mirror / Atom feed
From: murtuja bharmal <murtuja_bharmal@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.6 kernel module compilation without using KBUILD
Date: Wed, 28 Nov 2007 00:09:51 -0800 (PST)	[thread overview]
Message-ID: <299272.92165.qm@web36708.mail.mud.yahoo.com> (raw)

Hello All,
   
I want to compile external linux kernel module without
using KBUILD.
I tried to find out whole process of kernel module
compilation using KBUILD after enabling flag 
KBUILD_VERBOSE=1.
   
If we look at 2.6 kernel module building process.
   
1. gcc is making ".hello.o.d" and ".tmp_hello.o"
   from "hello.c" file.
2. Creating "hello.o" file using ".hello.o.d"
   and ".tmp_hello.o". 
3. Running Script "scripts/mod/modpost" to
   create "hello.mod.c" using “hello.o”.
4. gcc is making "hello.mod.o" after compiling 
   "hello-mod.c" file.
5. finally "ld" is linking "hello.o"
   and "hello.mod.o" and making "hello.ko". 
   
Step 2 of above process is not very much cleared, how
it is making hello-2.o from ".hello.o.d" and
".tmp_hello.o".

What is ".tmp_hello.o”.
   
Do we have any document which describe how to make
kernel module without using KBUILD.
   
Any pointer of information is very helpful for me.
   
Thanks 
Murtuja Bharmal



      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

             reply	other threads:[~2007-11-28  8:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28  8:09 murtuja bharmal [this message]
2007-11-28  9:00 ` Linux 2.6 kernel module compilation without using KBUILD Sam Ravnborg
2007-11-28  9:53   ` murtuja bharmal
2007-11-28  9:56     ` Robert P. J. Day
2007-11-28 10:40       ` murtuja bharmal
2007-11-28 10:59     ` Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2007-11-28  6:11 murtuja bharmal
2007-11-28 10:00 ` Adam T. Bowen

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=299272.92165.qm@web36708.mail.mud.yahoo.com \
    --to=murtuja_bharmal@yahoo.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.