All of lore.kernel.org
 help / color / mirror / Atom feed
From: freeman.zhang1992@gmail.com (Freeman Zhang)
To: kernelnewbies@lists.kernelnewbies.org
Subject: cannot insmod sculld in ldd3
Date: Mon, 13 Mar 2017 12:19:58 +0800	[thread overview]
Message-ID: <00355f0a-57da-e530-2ada-94b5eb9faeff@gmail.com> (raw)
In-Reply-To: <20170312190304.GA10105@kroah.com>

Hi Greg,


On 3/13/17 3:03 AM, Greg KH wrote:

> 
> 'depmod' handles all of this when you install a kernel and its modules.
> 

Thanks for that information, now I take 'depmod' seriously and stop
making up inelegant methods. I studied the 'kmod', both its behaviors
and codes, and got plenty of ideas about module symbol stuff.

However, I am still wondering why copy Module.symvers file works too, at
building time?

>	step 1.   build lddbus, generate `*.ko` and `Module.symvers`
>	step 2.   copy `Module.symvers` located in lddbus directory
>	          to sculld directory
>	step 3.   build sculld


All the best!
Freeman


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: OpenPGP digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170313/e8a4cf98/attachment-0001.bin 

  reply	other threads:[~2017-03-13  4:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 18:12 cannot insmod sculld in ldd3 Ali Aminian
2017-03-12 19:03 ` Greg KH
2017-03-13  4:19   ` Freeman Zhang [this message]
2017-03-13  8:32     ` Greg KH
2017-03-13 13:44 ` Aruna Hewapathirane
  -- strict thread matches above, loose matches on Subject: below --
2017-03-12  3:17 Ali Aminian
2017-03-11 21:49 Ali Aminian
2017-03-10 16:49 Ali Aminian
2017-03-10 18:06 ` valdis.kletnieks at vt.edu
2017-03-11 22:58 ` Tobin C. Harding
2017-03-12  8:55 ` Freeman Zhang

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=00355f0a-57da-e530-2ada-94b5eb9faeff@gmail.com \
    --to=freeman.zhang1992@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 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.