kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Out-of-tree module build in a dedicated build directory.
Date: Thu, 15 Mar 2018 17:26:45 +0100	[thread overview]
Message-ID: <20180315162645.GA2450@kroah.com> (raw)
In-Reply-To: <CAFSeFg8ckro4NW+_hGv8O_UjfVUVSxrqchnxQifC6ti+XyYw5Q@mail.gmail.com>

On Thu, Mar 15, 2018 at 11:27:05AM -0400, Aruna Hewapathirane wrote:
> On Thu, Mar 15, 2018 at 10:52 AM, Aruna Hewapathirane <
> aruna.hewapathirane at gmail.com> wrote:
> 
> > <snip>
> >
> >>
> >> But the issue remain the same:
> >> $ make
> >> make -C /home/lexa/linux M=/home/lexa/module
> >> O=/home/lexa/module/build_x86 modules
> >> make[1]: Entering directory '/home/lexa/linux'
> >> make[2]: Entering directory '/home/lexa/module/build_x86'
> >>
> >>   WARNING: Symbol version dump ./Module.symvers
> >>            is missing; modules will have no dependencies and modversions.
> >>
> > <snip>
> >
> > Please run make modules from the top level directory of your source tree
> > and and then module.symvers will be generated.
> >
> >
> If for some reason make modules did not create module.symvers then try:
> 
>         cd /home/lexa/linux
>         make
>         [wait a few minutes as it builds some scripts and starts building
> kernel code...]
>         hit <Ctrl-C>
> 
> then go back and try building your module.

'make modules_prepare' should do the same thing.

'make help' shows all of this, but who ever reads documentation :)

  reply	other threads:[~2018-03-15 16:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 12:14 Out-of-tree module build in a dedicated build directory Aleksei Fedotov
2018-03-15 13:00 ` Greg KH
2018-03-15 13:33   ` Aleksei Fedotov
2018-03-15 13:36     ` Denis Kirjanov
2018-03-15 14:01     ` Greg KH
2018-03-15 14:36       ` Aleksei Fedotov
2018-03-15 14:52         ` Aruna Hewapathirane
2018-03-15 15:27           ` Aruna Hewapathirane
2018-03-15 16:26             ` Greg KH [this message]
2018-03-15 16:39               ` Aleksei Fedotov
2018-03-15 17:14                 ` Greg KH
2018-03-15 18:58                 ` Aruna Hewapathirane

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=20180315162645.GA2450@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).