From: idoit.ief@gmail.com (Tayssir Alkowatly)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Compiling single module
Date: Wed, 27 Apr 2011 12:44:08 +0300 [thread overview]
Message-ID: <BANLkTi=tL+RHDYVyBgfgG=0mxV91zsL2nQ@mail.gmail.com> (raw)
In-Reply-To: <20110426132919.GA14149@kroah.com>
Hi All
I hope I'm enriching the discussion and not hijacking it
So what is the difference between
1- make M=./drivers/staging/tm6000 modules
2- make ./drivers/staging/tm6000/tm6000.ko
because from (1) I get linking error (ld: no input files), while I get a
module that cannot be inserted (Invalid format, no symbols in module_layout)
from (2) on kernel 2.6.35
Cheers,
Tayssir
2011/4/26 Greg KH <greg@kroah.com>
> On Tue, Apr 26, 2011 at 05:41:12AM -0700, Ezequiel Garc?a wrote:
> > I think maybe this is because I need to enable the module by on config.
> > Am I right?
>
> Yes.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110427/c4695f93/attachment.html
next prev parent reply other threads:[~2011-04-27 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 12:12 thinking of updating the canonical online udev document Robert P. J. Day
2011-04-26 12:41 ` Compiling single module Ezequiel García
2011-04-26 13:29 ` Greg KH
2011-04-27 9:44 ` Tayssir Alkowatly [this message]
2011-04-27 16:27 ` Mulyadi Santosa
2011-04-26 12:54 ` thinking of updating the canonical online udev document Greg KH
2011-04-26 13:05 ` Mandeep Sandhu
2011-04-26 13:31 ` Greg KH
2011-04-26 13:59 ` Mandeep Sandhu
2011-04-26 13:06 ` Robert P. J. Day
2011-04-26 13:32 ` Greg KH
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='BANLkTi=tL+RHDYVyBgfgG=0mxV91zsL2nQ@mail.gmail.com' \
--to=idoit.ief@gmail.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).